Frank Purcell
unread,Jul 4, 2012, 12:40:01 AM7/4/12Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Sarah Matthews, opentrippl...@googlegroups.com
There are a lot of variables (like the size of your Graph.obj, the number of requests, the OS you're using, your expectations on number of users and uptime, etc...); if OTP is just for you to do local testing, I would say that 4G of RAM is probably fine. But if you're looking to host OTP for others to use, then your probably on the bottom end of a workable OTP stack. (Note that I'm specifically speaking about the routing api -- no experience running the analytics app).
On my macbook air (which has 4GB of ram, to which I give tomcat / winstone 2GB of heap), OTP runs fine for just myself, and I don't see 4GB of physical memory as limiting at all. But in production on a server intended for multiple users, I have found that giving the OTP api 4GB (e.g., -Xmx4096m) of memory on it's own dedicated tomcat instance works best . I've see the production api instance reach 2.9GB after running for a month or so with a load of say 100 trip plans per day ... I've gotten that number to rise to ~3.7GB when I stress-tested the api under a constant load for over 24 hours (100 different trip plan urls). The memory usage of OTP appears to stabilize at these numbers, and I've got confidence that the memory usage is fairly predictable. (I'll know more next month when I send a lot more real users, ala ~2000 per day, to OTP). And note that I have another 8GB of memory on that server for other tasks, like the OS, the map webapp, etc... I've not seen the server dip into virtual memory with this configuration, load, etc...
On Jul 3, 2012, at 7:29 PM, Sarah Matthews wrote:
> Hi
>
> Just wondering is any RAM usage for the otp, please? My hosting currently has 4GB RAM and looks still not enough, is anyone had some issue, please?
>
> XXXX