I have a web page being served by v8. If I put a large load on it, the garbage collector executes very often and creates poor response times: http://s3.amazonaws.com/four.livejournal/20090529/timeseries6.png
If I have use the --trace_gc option I see this output like this: Mark-sweep 8.8 -> 1.5 MB, 17 ms. Mark-compact 8.8 -> 1.5 MB, 35 ms. Mark-sweep 9.5 -> 1.5 MB, 14 ms. Mark-sweep 8.8 -> 1.5 MB, 15 ms. Mark-sweep 8.8 -> 1.5 MB, 15 ms. Mark-sweep 8.8 -> 1.5 MB, 15 ms. Mark-sweep 8.8 -> 1.5 MB, 16 ms. Mark-sweep 8.8 -> 1.5 MB, 16 ms. Mark-sweep 11.5 -> 1.6 MB, 40 ms. Mark-sweep 11.6 -> 1.6 MB, 22 ms. Mark-sweep 11.5 -> 1.6 MB, 21 ms. Mark-compact 11.6 -> 1.6 MB, 42 ms. Mark-sweep 11.7 -> 1.6 MB, 21 ms. Mark-sweep 11.6 -> 1.6 MB, 21 ms. Mark-compact 11.6 -> 1.6 MB, 61 ms. Mark-sweep 11.8 -> 1.6 MB, 21 ms. Mark-sweep 11.6 -> 1.6 MB, 21 ms. Mark-compact 11.6 -> 1.6 MB, 42 ms. Mark-sweep 11.7 -> 1.6 MB, 21 ms. Mark-sweep 11.5 -> 1.6 MB, 21 ms. Mark-compact 11.6 -> 1.6 MB, 39 ms. Mark-sweep 11.8 -> 1.6 MB, 21 ms. Mark-sweep 11.5 -> 1.6 MB, 22 ms. Mark-compact 11.6 -> 1.6 MB, 39 ms. Mark-sweep 11.7 -> 1.6 MB, 20 ms. Mark-sweep 11.6 -> 1.6 MB, 24 ms. Mark-compact 11.5 -> 1.6 MB, 40 ms. Mark-sweep 11.8 -> 1.6 MB, 21 ms. Mark-sweep 11.6 -> 1.6 MB, 21 ms. Mark-compact 11.5 -> 1.6 MB, 45 ms. but it doesn't mean much to me. I wonder if anyone has some tips about getting the garbage collector to run less frequently. thanks --~--~---------~--~----~------------~-------~--~----~ v8-users mailing list [email protected] http://groups.google.com/group/v8-users -~----------~----~----~----~------~----~------~--~---
