FAQ
Quit new to node ....

Case: An Express based rss server, with custom caching mechanism. (An
Object array) Works flawless.
The data comes from a mysql server, defined in a module.

Under heavy load one cpu core exceeds 100%, due to the database calls.

Just clustering the whole server is no solution, every instance is creating
its own cache data.

Is it possible to cluster only the database module?

Like: Starting 4 childprocces, send a request for data to one of the
processes and respond to the same request.


--
Job Board: http://jobs.nodejs.org/
Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Search Discussions

  • Imre_b at Jun 27, 2012 at 4:15 am
    Found my solution in 'backgrounder'. Quit simple to start a custom module
    as background process.

    Imre

    Op zondag 24 juni 2012 01:19:23 UTC+2 schreef Imre_b het volgende:
    Quit new to node ....

    Case: An Express based rss server, with custom caching mechanism. (An
    Object array) Works flawless.
    The data comes from a mysql server, defined in a module.

    Under heavy load one cpu core exceeds 100%, due to the database calls.

    Just clustering the whole server is no solution, every instance is
    creating its own cache data.

    Is it possible to cluster only the database module?

    Like: Starting 4 childprocces, send a request for data to one of the
    processes and respond to the same request.


    Op zondag 24 juni 2012 01:19:23 UTC+2 schreef Imre_b het volgende:
    Quit new to node ....

    Case: An Express based rss server, with custom caching mechanism. (An
    Object array) Works flawless.
    The data comes from a mysql server, defined in a module.

    Under heavy load one cpu core exceeds 100%, due to the database calls.

    Just clustering the whole server is no solution, every instance is
    creating its own cache data.

    Is it possible to cluster only the database module?

    Like: Starting 4 childprocces, send a request for data to one of the
    processes and respond to the same request.


    Op zondag 24 juni 2012 01:19:23 UTC+2 schreef Imre_b het volgende:
    Quit new to node ....

    Case: An Express based rss server, with custom caching mechanism. (An
    Object array) Works flawless.
    The data comes from a mysql server, defined in a module.

    Under heavy load one cpu core exceeds 100%, due to the database calls.

    Just clustering the whole server is no solution, every instance is
    creating its own cache data.

    Is it possible to cluster only the database module?

    Like: Starting 4 childprocces, send a request for data to one of the
    processes and respond to the same request.

    --
    Job Board: http://jobs.nodejs.org/
    Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
    You received this message because you are subscribed to the Google
    Groups "nodejs" group.
    To post to this group, send email to nodejs@googlegroups.com
    To unsubscribe from this group, send email to
    nodejs+unsubscribe@googlegroups.com
    For more options, visit this group at
    http://groups.google.com/group/nodejs?hl=en?hl=en

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupnodejs @
categoriesnodejs
postedJun 24, '12 at 1:04a
activeJun 27, '12 at 4:15a
posts2
users1
websitenodejs.org
irc#node.js

1 user in discussion

Imre_b: 2 posts

People

Translate

site design / logo © 2022 Grokbase