dwood, thanks for the feedback. The problem is that the import is a very sql-intensive operation (lots of tiny disc reads & writes), so I’m working on optimizing that. The process flow looks something like this in 1.8.3:
1. get the image metadata (a read from the disk)
2. check the ewwwio_images table for an entry (another read from the disk)
3. create/update the record for the image in the ewwwio_images table (a write operation, which is typically more intensive).
Repeat this once for every image in WordPress, and it can take a looooooong time.
The new process is going to look like this:
1. get the image metadata for all images at once
2. retrieve all the entries in the ewwwio_images table
3. do updates on demand, but do record creation in batches of 100+
For something like 10,000 images, this will result in 2 read operations, and 100 write operations, a HUGE improvement over the previous process.
The last step thing I have to implement is the multi-record INSERT statements. Going to work on that this morning hopefully so I can get it pushed out by tomorrow at the latest.