I've googled for some while, but fail to find an approach to break v8's
heap limits. I need to handle a very big key-value object and nodejs's
object manipulation is very fast (about 10x faster than python dict), so is
it possible to break though v8's ~2GB heap limits at current stage or in
the
Meinfelder wrote:
>
> By any chance are you using a 32-bit version v8? What version of node are
> you using?
>
> -Edmond
>
>
> On Aug 20, 2013, at 2:06 AM, NStal Loit >
> wrote:
>
> > I've googled for some while, but fail to find an approach to break
Well, using buffer is not a good choice for my use case, because in my
project, the bottle neck is not the data itself but the data index. I use
v8 object as sort of in-memory db.
If I have to use buffer or manipulate index/hash my self, then I'm likely
to do this in c++ or with redis. But proba
Thank you peter, C++ binding is another choice I would consider, if I make
sure it's hard to remove v8 heap limit right now or in near future and
split process has unacceptable overhead.
On Thursday, August 22, 2013 1:23:21 PM UTC+8, Peter Rust wrote:
>
> > as well as quite a few others on npm
Marcel ,
I forgot to mention that. This option in node is actually
--max_old_space_size according to the node's manpage, but not work for me
when greater than ~2G.
During my search and test, I found this option only useful to remove the
soft limit in old days (say node 0.6). It likely becaus
`fs.watch` are not capable to tell difference between the folder change or
the child change when watching the folder.
When I have a folder `bob`, and a file `bob/bob` under the folder. Both
unlink `bob/bob` or rmdir `bob` make the same result invoking the
callback("rename","bob");
I create
