Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Running a file/image server on a lowend VPS?
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Running a file/image server on a lowend VPS?

Have you guys tried to run an image server on a lowend VPS, I was thinking of at least a 512MB or 1GB ram VPS?

The server will not do any further processing, there will be a frontend server that will handle the image processing and upload it to the image server. The image server will only handle HTTP requests for displaying the image.

Software stack will only be nginx, php and webmin/virtualmin. How many requests can a 512mb and 1gb vps can handle, assuming a 255kb average size per image?

Comments

  • Try it, thats the best benchmark you could get.

    Thanked by 1yomero
  • What would you need PHP for? If it will be serving just images, nginx will do.

  • Install the software and use something like apachebench to test it.

    Do you really need webmin/virtualmin for something as simple as nginx and PHP?

  • @Traffic said:
    What would you need PHP for? If it will be serving just images, nginx will do.

    I guess he wants to run something like imgur

    Thanked by 1Traffic
  • exception0x876exception0x876 Member, Host Rep, LIR

    @sanmax88 said:
    How many requests can a 512mb and 1gb vps can handle, assuming a 255kb average size per image?

    A lot assuming you will use nginx with sendfile

  • @Traffic said:
    What would you need PHP for? If it will be serving just images, nginx will do.

    PHP for API

    @hostnoob said:
    Install the software and use something like apachebench to test it.

    Do you really need webmin/virtualmin for something as simple as nginx and PHP?

    Makes management easier for me

    @exception0x876 said:
    A lot assuming you will use nginx with sendfile

    Ok, will check this also

  • @sanmax88 said:
    PHP for API

    What API? Take a lesson from the big guys and realize that unless you need some sort of strict management of the images, you'd do well to consider serving them up as static data. For many applications, a URL with something like a UUID as part of the path/name is sufficient to keep unwanted eyes from prying.

  • Give loader.io a go.

    http://www.lowendtalk.com/discussion/65252/stressing-a-wordpress-installation-on-scaleway-c1

    Also browser caching is useful.

    expires 2w;
    add_header Cache-Control "public";
    
  • yup got that right, need it to connect with the frontend server and for management of the uploads. there's a different and bigger software at the frontend, so can't do without the API end of the image server.

Sign In or Register to comment.