Loading Profile...
How large a library will DL2 support?
My DL2 libraries consist of 4676 books, 1413 movies, and 7016 iTunes albums.
DL2 crashes with Uncaught System Exception Signal 10 & 11 errors when I try publishing more than 2000 items, and I can't print a PDF using the Details style, just trying to output the movies library (1413 items) causes DL2 to lock up.
Has DL2 reached its limit or is it a bug? Or is my Mac (Dual 2.7 GHz PPC G5 w/2.5 GB RAM) not up to the task?
DL2 crashes with Uncaught System Exception Signal 10 & 11 errors when I try publishing more than 2000 items, and I can't print a PDF using the Details style, just trying to output the movies library (1413 items) causes DL2 to lock up.
Has DL2 reached its limit or is it a bug? Or is my Mac (Dual 2.7 GHz PPC G5 w/2.5 GB RAM) not up to the task?
I’m feeling doubleplus ungood
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?Sorry you're having trouble... I'm working on publishing large collections.
When you've got that many images that you're outputting at once, you're talking about BIG files, and that requires some finesse in programming. There's no fixed limit per se, but if you run out of VM space, you'll crash.
There are tricks I can do to keep VM smaller, and I'll be doing those as I refine publishing and printing.
Did you import your collection from Delicious Library 1? That makes publishing a bit harder on the DL2, because it's not sure if you have a "standard" cover or not.
The company says
this answers the question
-
Inappropriate?Thanks for the reply! Yes, most of my DL2 library was imported from DL1 but I don't understand why that would be a problem or what you mean by a "standard cover". When you say DL2's running out of virtual memory, would adding more RAM help?
I’m perplexed
-
Inappropriate?So, the problem is, when DL2 imports a library from DL1, it isn't sure if the cover images are from Amazon are were set by you -- I didn't keep track of this in DL1, and I store the images differently in DL2 so I can't just compare them.
I keep the DL1 image around in DL2 until you inspect the item, then I'll replace it with the latest Amazon version. When this happens, I also store the URL of the Amazon image, which is very important, because then when I publish you library to the web I don't have to write out the actual image file -- I can just write the URL of the Amazon image.
So, if you have 2000 items from DL1 which don't have updated images, you'll write 2000 images to a single file (in 2.0.2), and might exceed the hard limits on virtual memory. This is what I think is happening, anyhow. Adding RAM won't help this, as it's a 32-bit OS problem. (I wasn't able to go full 64-bit with DL2 because I was missing some key libraries at ship time.)
If your 2000 items all have covers that were updated in DL2, they won't write their images to the share file, they'll just write the URLs, and that should be a lot smaller. (They'll still write thumbnails to the website, and that might get too large, but I don't think so.)
I know, it stinks there's all this complication. I'm working to make this simpler in 2.0.3 and beyond. Honestly, it's tricky to publish this much data at once.
-W
1 person says
this answers the question
EMPLOYEE
