View Single Post
Old 12-14-2009, 11:52 AM   #20
dpierron
calibre2opds guru
dpierron shines like a glazed doughnut.dpierron shines like a glazed doughnut.dpierron shines like a glazed doughnut.dpierron shines like a glazed doughnut.dpierron shines like a glazed doughnut.dpierron shines like a glazed doughnut.dpierron shines like a glazed doughnut.dpierron shines like a glazed doughnut.dpierron shines like a glazed doughnut.dpierron shines like a glazed doughnut.dpierron shines like a glazed doughnut.
 
dpierron's Avatar
 
Posts: 533
Karma: 8792
Join Date: Aug 2005
Location: Metz, France
Device: iPhone, iPad, PRS-650
Quote:
Originally Posted by itimpi View Post
Maybe you should add soething about the RAM requirements v Library size to the README file? You do not want to make the tool grab a lot of RAM for those who have much smaller libraries so simply telling people what to do if the error requires might be the way forward?
Well, technically you're correct, but I would end up generating multiple batch files to start the application with different RAM sizes ; in the end, the user would have to choose which one to run, and become aware of this very technical thingie, which he does not want to...

I think that 256 Mb of RAM is a very small chunk of most modern computers, especially with virtual memory ; also, the tool is meant to run a few times every hour or day, and will be running for 5 to 20 seconds on most computers.

So, IMHO, leaving this as the default value is perfectly acceptable, and the advanced users who know they don't need as much and want to minimize the tool's impact on their computer can edit the script...

Anyway, thanks for pointing out the problem, I have such a small library (176 books) that it would never have happened to me

Regards,
David.

PS: I took for granted that you used Windows, but the edit I mentionned works also in the Unix shell script that resides in the same directory, of course...
dpierron is offline   Reply With Quote