Colin wrote:
...a record cache which will then write to the database file on shutdown of the application.
BEE MBA PMP SCJP-6
Jim Hoglund wrote:this design choice could result in a failing grade.
BEE MBA PMP SCJP-6
Colin Duggan wrote:Any other suggestions as how i could handle this OOM? Thanks
Jim Hoglund wrote:Can you share your reasons for leaving the booking data unsaved.
BEE MBA PMP SCJP-6
Roel De Nijs wrote:
Colin Duggan wrote:Any other suggestions as how i could handle this OOM? Thanks
If you get an OutOfMemoryError there is little you can do. Your server/application can't recover from this error (that's why it is an error and not an exception). That's a possible drawback of using a record cache. Just mention it in your choices.txt as a possible drawback and maybe suggest some solution and you'll be fine.
SCJP 5, SCWCD 5, SCBCD 5
Jonathan Elkharrat wrote:try running the tests with a bigger heap size. (-Xmx 1024m for example)
Cheers, Roberto Perillo
SCJP, SCWCD, SCJD, SCBCD
SCJP 5, SCWCD 5, SCBCD 5
SCJP 5, SCWCD 5, SCBCD 5
SCJP 5, SCWCD 5, SCBCD 5
SCJP 5, SCWCD 5, SCBCD 5
Jonathan Elkharrat wrote:that was just a suggestion, a collection can quickly cause OOM error if not managed correctly...
Colin Duggan wrote:A bottle neck still exists in the lock method when a large number(running 8000+ iterations) of threads are waiting on the same lock object. I think this is just something I'm going to have to justify and provide possible work around for in my choices.txt?
I carry this gun in case a vending machine doesn't give me my fritos. This gun and this tiny ad:
Free, earth friendly heat - from the CodeRanch trailboss
https://www.kickstarter.com/projects/paulwheaton/free-heat
|