24/7 Proxychecking. VPS good enuff?

[c0ff3h]

I need some help here. The plan is to have proxyfire running 24/7 on this vps with alot of threads.
But I don't know what to choose. My budget is tiiight.

Do you guys think I'll do fine with the $15 vps from xsservers
Specs: 2GHZ, 256mb RAM, 100mbit(shared)

I personally think it's too crappy to handle it due too the bad ram. But you can always hope. What do you think, good enough?

 

[Autumn]

I'm not familiar with Proxyfire but for my own proxy checking setup (which is written in PHP), I require a lot of RAM because of the high number of threads. I'd recommend high RAM over processor speed; you don't need much CPU because most of the time is spent waiting for proxies to return data, but you do need lots of RAM if you want to run a lot of threads, regardless of the application.

Personally the server I use for testing peas (amongst other things) is a quad core xeon with 8GB RAM. However I batch it up and only do a scraping and testing run every hour. Individual proxies are always tested again right before they're used of course.

 

[c0ff3h]

I'm not familiar with Proxyfire but for my own proxy checking setup (which is written in PHP), I require a lot of RAM because of the high number of threads. I'd recommend high RAM over processor speed; you don't need much CPU because most of the time is spent waiting for proxies to return data, but you do need lots of RAM if you want to run a lot of threads, regardless of the application.

Personally the server I use for testing peas (amongst other things) is a quad core xeon with 8GB RAM. However I batch it up and only do a scraping and testing run every hour. Individual proxies are always tested again right before they're used of course.

Our definition of lots of threads may differ, hehe
I was thinking like 80-100 threads for leeching, while parallelly 350 check.

Will the $35 vps at xss handle it well you think?

 

[Autumn]

YMMV because I suspect Proxyfire is written in a compiled language that is probably less RAM hungry than my amateur PHP scripts, but I use 2000 threads for checking (60-80K proxies per run) and that takes about 4GB RAM including the RAM used by the OS (FreeBSD). Your OS RAM usage is going to be slightly higher since you'll be running Windows but I suspect that the $35 plan with 1GB RAM would be ok. You might be pleasantly surprised, or if it sucks you can always upgrade, or just lower your thread count. It all depends on how memory efficient Proxyfire is though. Roughly $1 per day for all the proxies you can use is still a pretty good deal though.

 

[c0ff3h]

YMMV because I suspect Proxyfire is written in a compiled language that is probably less RAM hungry than my amateur PHP scripts, but I use 2000 threads for checking (60-80K proxies per run) and that takes about 4GB RAM including the RAM used by the OS (FreeBSD). Your OS RAM usage is going to be slightly higher since you'll be running Windows but I suspect that the $35 plan with 1GB RAM would be ok. You might be pleasantly surprised, or if it sucks you can always upgrade, or just lower your thread count. It all depends on how memory efficient Proxyfire is though. Roughly $1 per day for all the proxies you can use is still a pretty good deal though.

Thanks the help mate. I'll give it a go. Yea, it indeed is a good deal =)