Announcement

  •  » Requests
  •  » dealing with high cpu scripts (which are aborted by various providers)

#1 2006-08-25 17:24:28

neyret
Member
1970-01-01
1

dealing with high cpu scripts (which are aborted by various providers)

Various internet acces providers kill process which late too long. 30" is not rare.

E.g., generating thumbnail is known to be time consuming, so one has to list no more than 20-30 images in a row.

The problem is that the simple process of listing the images lacking thumbnails is long !
With 724 images, I can no longer succeded in running the first part of the "Miniature" script.

Suggestion:
these scripts with long loops should be written on a restart-on-error way (like asynchroneous refresh):
this consists in storing from time to time at some logical steps the context of what has been finished and what is yet to be done.
Thus, each reloading/reruning would let the job progress.

--
Fabrice

Offline

 

#2 2006-08-25 17:28:02

plg
Piwigo Team
Nantes, France, Europe
2002-04-05
13795

Re: dealing with high cpu scripts (which are aborted by various providers)

You're right. We have to work on a method to split search for required thumbnails. Unfortunately it's written it was reported in french, but bug 521 is related to this topic.

Offline

 
  •  » Requests
  •  » dealing with high cpu scripts (which are aborted by various providers)

Board footer

Powered by FluxBB

github twitter newsletter Donate Piwigo.org © 2002-2024 · Contact