I am a student and a hobby web developer,
I am developing a public portal and hence i need a VPS(Virtual Private Server) for good performance.
I have some doubts in VPS purchase.
i am planning to buy a VPS, conf:

another offer from same web hosting company

Both these offer vary a little like

Now my question is as there is very little difference in two of the offers should i buy 2 offer1 VPS servers(so that i will get 2 Dedicated ips and 20 GB space with same memory cap.) or 1 offer2 VPS (with 1 dedicated IP + 15GB space with same memory cap.).

will there be any better performance be achieved if i buy two servers with same configuration rather than one single server with equal-ant conf.??

Will i face any major difficulty while hosting a site on multiple servers (My idea was i will host web-server and python script on 1 server and MySQL on other server so the load can be managed equally. Correct me if i am wrong)

thank you in advance

I would call those ram offerings a bit low for what you would want for mysql and http on a shared server. Have you looked at any other hosting providers? Linode? Rackspace? Is a vps necessary? have you looked at say serverpronto or layeredtech for a physical server?

Sir, i don't know what configuration could handle the website as i am new in it! please suggest me traffic-hardware ratio for a VPS. what are the other factors i should keep in mind and why exactly i buy / don't buy a VPS. As if i buy shared hosting then i could not control the RAM usage limits.
PS: I am programming in Django, so believe it will not consume system resources too much for each query.

Hardware to traffic ratio can very pretty greatly depending on the configuration of the http daemon and the scripts running on it. The more modules being loaded into each thread/child the more memory it takes up and the less you can run on a given amount of ram. The first thing to do would be determine the memory usage of each thread of your apache while running your website, from that you can extrapolate how many running threads you can handle and from that a number of clients you can handle given a specific amount of ram. It also matters how you're running python as either a cgi or mod_python... there are a lot of factors to look at, it might be worthwhile to pick up a small development vds, tweak it to the configuration you expect to use on your primary host and do some sizing and measurement from that.

Sir, i got it! A final question! is there any trouble or issues will i face if i use more than one VPS for hosting my site?
An how is it possible to use multiple servers more efficiently.? Optimised for speed and performance!

If you're separating them by service-- say one runs apache and another mysql there is nothing really complex to setup or change except to make the daemons listen to the appropriate locations. If you're going to be running multiple instances of apache or a load balanced setup of some kind (and I'd recommend getting away from virtual machines before you do something like that) then things become a bit more complex but also notably faster. If you get to the point you need that stop back and we'll give you a hand

If you are proficient in Linux and especially in Debian then you might benefit from my own story. I also started small as a solo web developer but my love for Linux drove me to get a dedicated box and try to run everything myself. I spent a lot of time figuring things out, but being able to outperform much better funded and larger competition with raw expertise was worth the hassle. You can read my full article on this experience along with a few pointer on how to do the same your self as well as the info on which company I leased the machine from: How to have a cheap dedicated web server.

Moved: This thread is more suitable in Linux-Server and has been moved accordingly to help your thread/question get the exposure it deserves.

@jschiwal
thanks for moving this thread

@vsurlan
thank you for your valuable suggestion.. i am going through your blog entry.. will be heading towards purchase of my VPS in a week.

@vsurlan

this was a the best part, barely technical