Comment #47 on issue 847 by [email protected]: 1gb memory limit
https://code.google.com/p/v8/issues/detail?id=847
I'm working with a lot of files.
For now i can choose to use a very old version of node.js 0.10.22 that
seems more flexible regards to --max-old-space-size. But it still flats out
completely around 2-4 GB (probably 1.9GB)
However it doesn't crash. But is just very slow.
If i stream my file data to the database that i'm importing data to, i get
too many open files.
I can get around this issue in the folowing ways:
1. By refactoring my code to use synchronous file access, which is sad.
2. Use fs-gracefull. But it also causes memory issues and slow downs
because of file cueing.
3. Group all my files together in folders of about 10.000 - 20.000 files,
to match the node memory threshold. Then run multiple instances of node.js.
But marshalling +250.000 large files located in a nested folder structure
isn't always easy.
If concerns with mobile Android performance is holding back V8
optimizations, maybe an enterprise extension ( with enhanced data objects
etc. ) to V8 could be considered.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
