Hello v8-dev
I'm interested in assessing how close to the maximum heap size the old
generation has expanded. Neither the HeapStatistics nor the newer
HeapSpaceStatistics structures include this information (although
HeapStatistics does provide heap_size_limit(), it provides a total
Hello v8-dev
I'm interested in assessing how close to the maximum heap size the old
generation has expanded. Neither the HeapStatistics nor the newer
HeapSpaceStatistics structures include this information (although
HeapStatistics does provide heap_size_limit(), it provides a total
I have opened https://code.google.com/p/v8/issues/detail?id=3967 to address
the high CPU usage.
Regards
Michael
On Thursday, 8 January 2015 17:34:01 UTC, m.j.tun...@gmail.com wrote:
Hello folks, my name is Michael Tunnicliffe and I work for IBM. I have
been working on the PowerPC port of V8
Hi all
There seem to be some constraints on the way the CpuProfiler works.
The CpuProfiler is usually set to take samples every 1ms.
The CpuProfiler uses a lock-free unbounded queue to receive code events
from the VM thread (as
described in https://code.google.com/p/v8/source/detail?r=4706) to
Hi Ben
A few things I noticed about the CPU improvement change in Node 0.10.36:
* It does not appear to have been contributed upstream to V8
* It only changes POSIX platforms (Windows still uses Sleep(0) a.k.a. yield)
* It hasn't been fully carried forward to 0.12 (I plan to raise a pull
request
Hi Ben
A few things I noticed about the CPU improvement change in Node 0.10.36:
* It does not appear to have been contributed upstream to V8
That's because the 3.14 branch is dead and unsupported by the V8 team.
Right, but I thought this was a problem on the latest V8 release as well,
On Friday, 9 January 2015 11:26:29 UTC, Ben Noordhuis wrote:
Hi Michael,
On Fri, Jan 9, 2015 at 12:14 AM, m.j.tun...@gmail.com javascript:
wrote:
Hi Ben, thanks for your reply, I was a little worried because my initial
web
searches did not find obvious reports of this issue by
Hi Ben, thanks for your reply, I was a little worried because my initial
web searches did not find obvious reports of this issue by others (too much
noise perhaps).
For V8 3.14 / node.js v0.10, I fixed most of the overhead by means of
PR [0], what I think you call a poor man's hack in your
Hello folks, my name is Michael Tunnicliffe and I work for IBM. I have been
working on the PowerPC port of V8 along with Andrew Low and a number of
other colleagues. Recently, I have also been writing some code to use the
V8 API and have come across something that looks a bit strange to me.
