For a production server that needs to handle 10,000 concurrent users, what size Amazon servers and other services(like separate database) are needed to reliably serve them? A c3.xlarge(4 core 7.5 GB) + database per 10k?

The primary content are images and embedded links to other content providers like image hosting and youtube. Cloudflare will be utilized, is an nginx load balancer necessary?

At this level, does the redis need its own server? It certainly seems like it would in production; development the opposite being true. How big does redis get in production? Not a lot is said about Mongodb, that I can find in the forums. How do you persist data from redis to mongodb programmatically?

What additional third party software would help optimize the server to handle a large load? And, the workers would be # of CPUs + 1 on the application server? Are nodeBB workers stateless: Can I spin up spot micro-instances when demand is the highest for a hefty spot discount? What size are individual nodebb workers? (to better estimate application server memory needs)

The internet is awash in conflicting data on server best practices. I need specific information on server needs with NodeBB as the core component. How does one go from dev to prod with Nodebb?

Thanks for making a great realtime forum software!

One TB of offloaded data made me a fanboy. Just trying to dodge all the costs that I can in dev for an efficient production.

Cool idea

@AOKP said:

Well in my eyes there are several factors I would consider.
Do you ONLY want to run NodeBB or are there other applications running on the server as for example WordPress, which requires PHP or is the server dedicated for NodeJS?

Do you use SSL encryption?

Whats your webserver (NGINX would be perfect for this)?

How fast is your connection (mainly important for an end-user)?

So basically it is important what you actually want to do. If its about simply running and serving NodeBB to 10K connections it is not so hard, but if you want to run several tasks at once on as few servers as possible things are slightly different.

• PHP only for the cart software. All NodeBB + webRTC signal server

• Only Partial SSL; for cart

• Yes; NGINX

• Connection would be determined by AWS/GCE

I am looking to architect the hardware footprint as a scaling collection of minimally sized servers so that during lulls in traffic the costs drop to the core Reserved Instances.

Although some content will be created and stored locally, the vast majority of the content will be embedded links to other sites. It is almost all just http traffic; NodeBB, chat, etc. Even the local content is being largely offloaded with Peer5 and the chat with webRTC. Minimalism.

0.9 related?

Our dev site is down... admin account throws "user does not exist." Thought it was just the weekly token error, cleared chrome and restarted... not working. We take regular backups, not super concerned for our stuff. if you dont take backups? this could be bad.

Edit: back up; lost two days

@pichalite

hadnt noticed it... dang it lol i was thinking about group mods.

Realtime CMS

That reminds me, I was thinking that what we need is a knowledge base. Though this forum largely serves that purpose, a purpose-built knowledge base made to answer questions via a multiple of keywords would really be great.

The community could submit articles and edit them. There are open source wiki engines and knowledge base systems that could be used. The docs were created some time ago and are not living documents as much as wikis are. The docs should not go away, but a wiki could be added to by approved members in an adhoc fashion.

Everyone here knows important things from using the software. However, answering the same questions repeatedly will cause fatigue.

@Kowlin said:

@bitspook Just mark it for moderation, and the guys will do the rest.

Marked you for moderation

jk jk

A friend worked out some of the warnings and spaced out the classes. Love the drag effect; will be using it going forward. Thanks for your work on it.

/*Custom Composer Bar Tweak by Arc begin*/
.composer .resizer .trigger i:before {
content: "\f0c9";
cursor: n-resize;
}
.composer.maximized .resizer .trigger i:before {
content: "\f0c9";
cursor: n-resize;
}
.composer .resizer {
position: absolute;
width: 100%;
top: 10px;
height: 0;
cursor: n-resize;
}
.composer .resizer .trigger i {
margin-left: -10%;
position: relative;
color: #FFF;
font-size: 14px;
}
.composer .resizer .trigger {
position: relative;
display: block;
width: 110%;
height: 20px;
top: -10px;
margin: 0 auto;
margin-left: -11px;
background: #000;
background: rgba(0,0,0,0.1);
border: 0 solid #E4E4E4;
-webkit-border-radius: 50%;
-moz-border-radius: 50%;
-ms-border-radius: 50%;
-o-border-radius: 50%;
border-radius: 0;
line-height: 20px;
-o-transition:.3s ease-in-out;
-ms-transition:.3 ease-in-outs;
-moz-transition:.3s ease-in-out;
-webkit-transition:.3s ease-in-out;
transition:.3s ease-in-out;
}
.composer .resizer .trigger:hover {
background: #000;
background: rgba(0,0,0,0.2);
-o-transition:.3s ease-in-out;
-ms-transition:.3 ease-in-outs;
-moz-transition:.3s ease-in-out;
-webkit-transition:.3s ease-in-out;
transition:.3s ease-in-out;
}
/*Custom Composer Bar Tweak by Arc end*/

a jet setting bunch

Vegas, Turkey... I never go anywhere cool.

THAT one... is wearing clothes....

Take it off!

@Ryan-Oliver

oh... wait... too good... now i hate you.

@Kowlin said:

LGA 775

Intel Core 2 Extreme QX6850 Quad-Core Processor, 3 GHz, 8M L2 Cache, 1333MHz FSB, LGA775

301 Moved Permanently

(www.amazon.com)

That is often far more of a benefit that many around me would care to hear; blind faith, flag-waving, 'Merica-ness.

@bitspook said:

QX9650

http://cpuboss.com/cpus/Intel-Xeon-E5440-vs-Intel-Core2-QX9650

You may well be on to something.

http://www.youcpu.com/en/compare/Intel-Xeon-E5440-12M-Cache-2.83-GHz-1333-MHz-FSB/Intel-Core-2-Extreme-QX9650-12M-Cache-3.00-GHz-1333-MHz-FSB

though the e5440 takes a beating on the Passmark

fail2ban works against a lot of low-level nuisances.

Try running your URL through Cloudpiercer.org... if your origin IP is exposed, cloud-based mitigation is largely useless when DNS attacks are still such an effective threat. Not all the bad guys are only toting Low Orbit Ion Cannons.