rapture
My feedback
3 results found
-
3 votes
An error occurred while saving the comment An error occurred while saving the comment rapture
commented
Yes, I did know Java has a large overhead. Nothing you can really do there. Reduce memory footprint at the cost of performance I feel is a valid and acceptable trade off. For a background service that runs constantly, the time it takes to update half a dozen new songs every week or so is irrelevant, as long as it's done in a timely manner. I'd prefer it to have a lower net memory use and take longer to do the task.
Maybe this becomes an option within bliss? A simple drop down "Limit memory use to:" and on next start it's a smaller footprint. I was happy changing the bliss.bat file myself, but not all are comfortable with this.
Turns out the CPU usage was as my brother had dropped some songs into the directory and I didn't know, so it was in the working processes.
Working with WHS 2011 here, on a Athlon II X4 630, so definitely not a slouch. System is actually an old gaming PC with the video card out and extra hard disks. I agree with the the optimization conundrum, a never ending battle. How do we define a goal for successful optimization? What would be the easiest way to approach this issue?
rapture
shared this idea
·
-
30 votesrapture
supported this idea
·
-
22 votesrapture
supported this idea
·
That sounds great. Thanks!