If you setup the Cron as explained in: http://piwik.org/setup-auto-archiving/

The the reports should be pre-processed. Make sure you run the cron every hour. Also in the General Settings set a timeout of 3000 seconds. This should ensure that the reports are not processed more often than needed. If they take few minutes to load, it means the archiving is triggered.

Sorry but cron archiving is set up correctly and web archiving is disabled. If web archiving is disabled it should never run into it, right?
Also its only doing that for the keywords, nothing else.
The cron job is running every 6 hours and the timeout is set to 21.600 seconds because of that.

Sorry didnt see that you ts77 created the ticket!

I really don't understand the problem (low volume site, + pre-processed, should never take 10 minutes)

Can you try upgrade to 1.12 ? this might fix it.

Also you can enable [log] in the config.ini.php and add &debug=1 in the URL to see if it is triggering archiving?

finally, could work to try with XHPROF to see where it's spending so much time.

Thanks for the pointers!

I got some debugging, and it recognizes it as being archived, still using LOTS of memory, just an excerpt here:

[2013-06-04 11:41:06] [eee8136d] [6.03 Mb] Already processed, fetching idArchive = 1188 (idSite=49), for month (2013-04), plugin Referers, Visits = 2998
[2013-06-04 11:41:06] [eee8136d] [9.71 Mb] Already processed, fetching idArchive = 1188 (idSite=49), for month (2013-04), plugin Referers, Visits = 2998
[2013-06-04 11:41:06] [eee8136d] [9.86 Mb] Already processed, fetching idArchive = 1188 (idSite=49), for month (2013-04), plugin Referers, Visits = 2998
[...many similar lines here...]
[2013-06-04 11:46:52] [eee8136d] [2,401.32 Mb] Already processed, fetching idArchive = 1188 (idSite=49), for month (2013-04), plugin Referers, Visits = 2998

What could be possibly wrong to get that many results? Shouldn't there be just one entry per month?

Sorry for delay, contact me by email for urgent matters in future.

There seems to be some kind of loops going on here. Do you flat=1 or expanded=1 maybe ?

Yes, as the request above has shown its using flat=1. Digging deeper thats the "flat" view of the keywords widget.
Is that how its supposed to work? If so, is there a way to disable that completely?

To disable flattener try the following:

+++ core/API/DataTableManipulator/Flattener.php (revision )
@@ -45,6 +45,7 @@
      */
     public function flatten($dataTable)
     {
+        return $dataTable;
         if ($this->apiModule == 'Actions' || $this->apiMethod == 'getWebsites') {
             $this->recursiveLabelSeparator = '/';
         }

Does it fix the issue?

In any case it would be good if we could understand this bug, as I have not seen it before (or even heard in the forums)

Please reopen if the bug persist in 2.0 codebase from git.