http archive request should pre-process listed segments in reasonnable fashion #3658
Labels
Task
Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
worksforme
The issue cannot be reproduced and things work as intended.
Milestone
In few words :
the archive.php script does implement // request for segment, but does not implement any queue mechanism which makes it unusable with many segments.
Long story : http://forum.piwik.org/read.php?3,97712
(with background cli task version being much much faster)
Current proposal http only :
"the logic used for queue is trivial : add x item to queue, then throw all requests and grab the result. This could be "optimized" to add x item to queue, then throw all queued requests and constantly check for result and add new requests as we remove them.
I quote optimize because I also think that this is debatable. Since the archiving server is likely to be the tracking server itself, your probably do not want to overload it. Current option goes in that direction since the average // request number will be lower than the maximum set and there will be tiny breaks to allow the rest of the server tasks to go on.
This of course only mean something with segment (the more segment, the more meaning) since otherwise queuing just does not occur at all (one single request at a time). "
The text was updated successfully, but these errors were encountered: