PS:

[1] https://github.com/oaeproject/Hilary

On Wed, Dec 31, 2014 at 10:46 AM, Branden Visser <[email protected]> wrote:
> Probably the two most important things I've used as a guide is that
> Node.js is single threaded (a single process cannot benefit from
> multiple CPUs) and very low memory footprint.
>
> Anecdotally, in my experience performance testing the Open Academic
> Environment [1], an application that does relatively little business
> logic and has no local caches, I haven't been able to push it above an
> 80Mb memory footprint before it becomes bound by IO or CPU.
>
> I would start with an Amazon t1.micro or Joyent xsmall (~512Mb of
> memory and 1 CPU) and performance test a single process. Decide how
> you need to scale thereafter based on how much load it can sustain
> (are you I/O bound? Memory bound?). Remember you also probably want
> monitoring tools to run on the machines, configuration management,
> etc... Which will impact how much memory and CPU you want on those
> VMs, so just test test test under those conditions.
>
> Hope that helps,
> Branden
>
> On Tue, Dec 30, 2014 at 5:32 PM, Sapardee <[email protected]> wrote:
>> May hapijs meets your need.
>>
>> On 31 Dec 2014 03:26, "Emroz Habib" <[email protected]> wrote:
>>>
>>> Currently we are in the process of developing an orchestration layer using
>>> Node. this layer will act as a façade to reach out multiple
>>> services/datasource to compose client specific response.
>>>
>>> Is there any nodejs sizing information available today that we would be
>>> able to use as a starting point.
>>>
>>> Any kind of help is greatly appreciated.
>>>
>>> Thanks
>>>
>>>
>>> --
>>> Job board: http://jobs.nodejs.org/
>>> New group rules:
>>> https://gist.github.com/othiym23/9886289#file-moderation-policy-md
>>> Old group rules:
>>> 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 unsubscribe from this group and stop receiving emails from it, send an
>>> email to [email protected].
>>> To post to this group, send email to [email protected].
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/nodejs/32e1c4cb-e313-43eb-a91f-5ab85803663b%40googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> Job board: http://jobs.nodejs.org/
>> New group rules:
>> https://gist.github.com/othiym23/9886289#file-moderation-policy-md
>> Old group rules:
>> 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 unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To post to this group, send email to [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/nodejs/CAGXt7XDHnma_qMou-k2FGKXpLB5JqbkW1PWNM%2BBx%3DG5D%2B16u9g%40mail.gmail.com.
>>
>> For more options, visit https://groups.google.com/d/optout.

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/CAOo4ObqLcDG%2Biy0p1Vx%2BpDDVc1cnbznWdSM7ZPfrAkDhkATedg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to