Still I cant find ANY reason why apache gets so wrapped up in the import process.
The file is on disk
Nothing is in the access or error logs..so..clicking "import" does nothing to apache.
I dont have the skillset to PROVE it, but I would guess that this is an IO constraint to getting database work done...but I dont know how.
All I know is when I do an import/export, any high DB activity (I deleted a large dummy category to test this) apache2 jumps in to suck up a lot of CPU...while doing nothing observable.
Bookmarks