Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

VM forking #41

Open
yrashk opened this issue Jan 1, 2011 · 4 comments
Open

VM forking #41

yrashk opened this issue Jan 1, 2011 · 4 comments
Labels
feature idea

Comments

@yrashk
Copy link
Member

yrashk commented Jan 1, 2011

So we can possibly load balance between VMs? Keep in mind that V8 is single-threaded anyway.
@yrashk
Copy link
Member Author

yrashk commented Jan 1, 2011

...or cloning. Still, something to think about

@Licenser
Copy link
Contributor

I totally am for that! Concidering that you have multiple gen_server's for the VM's it would make sense they use seperate VM instances :)

@foobarto
Copy link

I've been playing around with the idea described in the LYSE which is a bit overly complicated and could be simplified. Still its a good solution for load balancing, far better than simple round robin for example.

@Licenser
Copy link
Contributor

Hi foobarto,
I think the main problem is that currently the v8 driver does only start one process, having multiple VM's currently only slows you down since the one process working with them has to schedule between the different scopes and vm's. That is unless something has changed :) recently

Regards,
Heinz

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature idea
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@yrashk @Licenser @foobarto