Quote:
Originally Posted by PatNY
In the case of CC, it think the compression is done to optimize import times and database size. Personally, I would be willing to sacrifice both as I have plenty of storage room and normally only import books a couple at a time. But I understand if Charles doesn't want to go in that direction. I was just wondering if maybe there was another way to get around it.
|
The space issue is secondary. The real issue is network time. The amount of data to transfer is proportional to Height x Width. In other words, if a 100x100 bit image takes time T, then a 200x200 will take 4T . When you have 1000 books, factors of 4 start to matter a lot, especially during the metadata update cycle.