Memory of Xojo Cloud Server


The memory shown on the sales page ( is it fully available for our applications?
For example, for the small Xojo Cloud Server, 512Mb are fully available for our applications?
(Or part of this memory is taken by the operating system and various tools?)

Thank you

That’s the amount of ram for the entire VPS.

ok, thank you Greg. The info page of Christian ( says 246 MB of available memory, and I suppose he has installed only 1 web app.

Or only one running at that time. Remember your apps are built as CGI apps and they will quit when there are no active users.

Also keep in mind that there is memory used by the operating system and our middleware.

Yes, I had actually assumed that the web app took only a few Mb. The rest is taken by the operating system and tools.
Without the web app, there must be about 250-260 MB free.
A real web app takes on average 30 to 120 MB with the database. On average, we can therefore upload one or two small web apps on the small server, there will be some memory for point operations, backups, operating system operations, etc…
Here, indeed, the memory management of CGI is useful.

The small one I have has 512 MB of swap space, so you can add that to the memory as I bet big parts of apache or Xojo are not present in memory always.

I wouldn’t count on that. If the VPS is swapping memory out to disk, things tend to get really slow.

Well, looking on my VPS there, it already swapped out 50 MB. And I would expect that big parts can be swapped out without a problem. I only need some part of apache, perl and my web apps to run.

Christian, I just see that there is now only 83 MB of RAM available on your server (, you know why?

Well, I have no idea what’s running there, but it seems to go up and down over hours.

I hope this is not a memory leak of this type <>

However, you apparently have a single page and CGI!

And the infos app is started nearly every time someone looks, so the app is quit and memory released in-between.

Send a couple of hundred http requests at the web app and watch the RAM get eaten up.

looking on my process list app, I think the infos app is running 12 times currently.
Probably 11 are dead and just latest one is used!?

[quote=71591:@Lee Page]Send a couple of hundred http requests at the web app and watch the RAM get eaten up.
I hope you are not surprised by that. Every session takes memory, even if it is short lived, and released some time in the future.

:slight_smile: not at all.

Makes sense to adopt session limits code side. Suprised that the HIDS/NIDS doesn’t pick up on the amount of http flood.

It does, but what you did could be considered legitimate traffic.

By the way, i suggest you get the server owner’s permission if doing that in the future. Flooding an app with hundreds of unexpected connections could easily crash an app if it’s still in testing or has database intensive methods.

It also screws with web access metrics.

perfectly legimate, legal and one does not require the Server owners permission to stress test a public website application.

Yes of course 600 http request all in one go from a single host. Yup

With all the marketing spin on how great, secure the Xojo cloud service is. I am sure that not just myself but others over the years have been here before
and historically anything realsoftware/Xojo have announced normally has to be halved, then halved again to get the truth of things.

There is very little or limited information on the new Xojo cloud service, no mention of PCI compliancy, SSL, security etc. Is this information available ???


Whether permission is required or not, If nothing else it would be a courtesy to let them know before firing off load testing though. Just a thought.

@Lee Page - the user agreement at LoadImpact SPECIFICALLY states that you will not use it to test any servers except ones that are under your control. Most tools like this have that restriction.

As far as specifics, have you looked at ?