Isolates was my last saving grace while doing NodeJS research. I am
attempting to do a proof of concept for a product I am working on.
Scenario:
10,000 distinct'ish workers on a single machine. As it stands I'd need to
spawn 10,000 separate nodejs instances which amounts to about 300 gigs of
On Wed, Jun 13, 2012 at 2:06 AM, Andrew Finnell
andrew.finn...@gmail.com wrote:
Isolates was my last saving grace while doing NodeJS research. I am
attempting to do a proof of concept for a product I am working on.
Scenario:
10,000 distinct'ish workers on a single machine. As it stands I'd
If you are looking to spawn 10k worker nodes all on the same machine, you
are probably doing it wrong. Try scaling out, instead of up. Maybe node
isn't the right choice for what you are trying to do.
As for spawning up several hundred instances of a node.js application,
we've put a lot of work
Thank you for the reply,
I did come across your product. So if you put any work into getting Google
to bring up your product, it worked.
I cannot use any application management system until I solve the problem of
being able to run 10,000 instances of an app. Ultimately I have control
over how
I'd recommend starting a new mailing list post explaining the problem you
are attempting to solve. Someone should be able to help guide you towards
the correct architecture.
Better to figure out a general solution before trying to figure out the
specific technical limitations of a potential
+1
Please start a new post and explain why you need 10k apps ( thats a huge
effing number in that context ); for a particular application, or just for
research?
On Tue, Jun 12, 2012 at 9:24 PM, Marak Squires marak.squi...@gmail.comwrote:
I'd recommend starting a new mailing list post
Hi Liam,
Jorge is working on it and I'm trying to help with the little time I have.
It should show up on GitHub soon. Stay tuned.
Bruno
On Thursday, March 1, 2012 9:41:15 PM UTC+1, Liam wrote:
Hey Jorge Bruno, any progress? Maybe you should just post what
you've got to github...
On Feb
Hi Liam,
The project exists but it is just an empty shell. I'm working with
Jorge to package/document and we'll publish soon.
We already published the JASON utility (https://github.com/xk/JASON)
but the threads part is still in the works. Stay tuned...
Bruno
On Feb 8, 12:21 pm, Liam
Jorge Chamorro wrote a native module to allow workers based on threads
and Isolates, and was planning to enable inter-thread communication
via Buffers. The workers don't provide the Node API, just a way to run
CPU-intensive JS out of the main thread.
He didn't release the code publicly, but
but has ultimately turned out to cause too much instability in node's
internal functionality to justify continuing with it at this time.
please specify, elaborate, explain or make note upon this conflict, as
if in warning to those who would have wished to pursue the cause
further.
--
Job
10 matches
Mail list logo
