Bingo! The attached script drives v8 gc mad. It eats up to 200Mb of RAM having just 2000 objects active. Actually, memory consumption oscillates by an order of magnitude, i.e. between 300Mb and 20Mb. Both on my Mac and my colleague's Linux it starts to hyperoscillate having queue size of 2000 and suddenly stops oscillating on 4000. I use trunk, revision 605.
On Oct 27, 2008, at 1:07 PM, Victor Grishchenko wrote: > I found v8 garbage collecting patterns quite entertaining. The > attached graph represents the number of currently allocated buffers. > Buffers are wrapped by JavaScript objects, so deallocation happens > on garbage collection. Due to the specifics of the program, it never > needs more than 5000 buffers at once (actually, 2000+). CPU > utilization is 2-5%. Still, out-of-memory is inevitable. > <v8-gc-graph.png> > > http://www.tribler.org/attachment/wiki/PEXCrawl/v8-gc-graph.png > > On Oct 24, 2008, at 9:47 PM, Victor Grishchenko wrote: >> My program fails with: >> ---------------------------------------------------- >> # >> # Fatal error in CALL_HEAP_FUNCTION >> # Allocation failed - process out of memory >> # >> >> Abort trap >> ---------------------------------------------------- > --~--~---------~--~----~------------~-------~--~----~ v8-users mailing list [email protected] http://groups.google.com/group/v8-users -~----------~----~----~----~------~----~------~--~---
drive-gc-mad.js
Description: JavaScript source
