I've been running tt-rss for quite some time now with only myself as a user.
Now I've opened it for registration although it's not been announced anywhere yet.
I'm looking for advice, some rule of thumb, on how much resources that might be required.
I'm mainly trying to figure out if the service will last the first 15(150?) users or not.
How many users do you have, and what resources is the setup consuming?
Myself I'm running this on a VPS with 256MB RAM, using lighttpd which consumes about 60MB resting.
Experience on resource requirements?
- fox
- ^ me reading your posts ^
- Posts: 6318
- Joined: 27 Aug 2005, 22:53
- Location: Saint-Petersburg, Russia
- Contact:
Re: Experience on resource requirements?
Well, entire tt-rss.org (incuding online) is running on a venerable Athlon64 3500+, 1.3GB RAM machine which is my testing box. Online has 60 users and 4210 feeds, I wouldn't say that it works fast but it's more or less usable.
I don't have much experience with VPSes, but with 256MB RAM and no swap I wouldn't expect to handle many users. It's worth mentioning that tt-rss isn't really built as a scalable multi-user application, it's a personal aggregator which happens to support multiple users. The idea is that you could install it for your friends, not compete with Google Reader.
I don't have much experience with VPSes, but with 256MB RAM and no swap I wouldn't expect to handle many users. It's worth mentioning that tt-rss isn't really built as a scalable multi-user application, it's a personal aggregator which happens to support multiple users. The idea is that you could install it for your friends, not compete with Google Reader.
Who is online
Users browsing this forum: No registered users and 1 guest