What environment we need?

500,000 to 1,000,000 what?

@akerl:

500,000 to 1,000,000 what?

Users per month

Users != Traffic.

How many hits per hour would be most helpful.

Also what sort of application stack will you be running?

@obs:

Users != Traffic.

How many hits per hour would be most helpful.

Also what sort of application stack will you be running?

CentOs 64 + LAMP.

But can't plan hits right now. May you suggest me approximate solution, please.

If you're serving a "Hello, World" page, the smallest Linode could handle billions of pageviews per month. It's impossible to give a recommendation with zero information on what your setup will be. Are you serving static content? Wordpress? Drupal? phpBB3? Custom code? The answer would be very different depending on what you're doing.

If you're talking about half a million to a million users, each producing many pageviews, then assuming you're not just serving up static content (at which point even a single 512 might suffice if your content fits in RAM), you're going to probably want to set up a load balanced setup with multiple front-end machines, multiple application servers, multiple database servers, etc. Linode does make this as easy as it gets, since you can nearly instantaneously spin up as many linodes as you need, and connect them all over the private network (don't pay for communication between them).

@Guspaz:

If you're serving a "Hello, World" page, the smallest Linode could handle billions of pageviews per month. It's impossible to give a recommendation with zero information on what your setup will be. Are you serving static content? Wordpress? Drupal? phpBB3? Custom code? The answer would be very different depending on what you're doing.

I have my own pure PHP+MySQL web-application running on CentOs 64.

It has around 6 generated pages which should be used very frequently.

One of those pages is "Search result".

Currently search also implemented in PHP.

Moreover, my users are from Asia and my Linode server in London.

So what you may advice?

Use a 32 bit linode I doubt you have need for a 64 bit.

Start at 512, configure it properly (max clients, not going overkill on mysql settings, php-apc etc), if you find you're running out of ram then upgrade to a 768 etc etc, upgrade times are only a few minutes normally.

As for London, Fremont maybe better latency wise it depends on which bit of Asia. If your users are closer to Japan then Fremont would be best, if you're closer to Europe then London.

@obs:

Use a 32 bit linode I doubt you have need for a 64 bit.

Start at 512, configure it properly (max clients, not going overkill on mysql settings, php-apc etc), if you find you're running out of ram then upgrade to a 768 etc etc, upgrade times are only a few minutes normally.

As for London, Fremont maybe better latency wise it depends on which bit of Asia. If your users are closer to Japan then Fremont would be best, if you're closer to Europe then London.

Sorry, why you recommend 32 bit? What is the point?

Unless you have more than 4GB of RAM available to you, what's the point of 64-bit?

@TheClient:

@obs:

Use a 32 bit linode I doubt you have need for a 64 bit.

Start at 512, configure it properly (max clients, not going overkill on mysql settings, php-apc etc), if you find you're running out of ram then upgrade to a 768 etc etc, upgrade times are only a few minutes normally.

As for London, Fremont maybe better latency wise it depends on which bit of Asia. If your users are closer to Japan then Fremont would be best, if you're closer to Europe then London.

Sorry, why you recommend 32 bit? What is the point?

32 bit uses less RAM.