07:27 <nikksno42> Hi there! I've used sandstorm several times in the past and I'd now like to suggest to you my newly created project as an addition to your amazing platform. It's called aenigma, and it's a fully functional and secure out-of-the-box XMPP server based on ejabberd. It's found here: https://github.com/openspace42/aenigma. It automatically sets up every

07:27 <nikksno42> thing needed, and could very well fit into your app deployment workflow, but of course it could be stripped down to fit an already organized environment like sandstorm [i.e. skip letsencrypt, nginx, et...]. If you like it, and / or would like to work on it together, let me know! Thank you so much in advance!

12:07 <fossterer> Hi! What system configurations are you running Sandstorm on? My basic Googee Cloud VPS seems very slow with just 4 webapps @channel

12:07 <fossterer> *Google

14:42 <ocdtr_web> fossterer: How much RAM do you have? That's usually the limitation folks run into.

14:43 <ocdtr_web> Sandstorm itself adds very little overhead to the performance of the applications on it, but each individual grain uses as much RAM as the application itself, since they're individually sandboxed. I.E.: Two open Etherpad grains will use about twice as much RAM as running an ordinary Etherpad server.

15:14 <fossterer> I'm running it on g1-small (1 vCPU, 1.7 GB memory). For one Etherpad instance at one time, do you think 1.5GB+ is not enough?

15:16 <fossterer> Also, ocdtr_web: Thanks for the info about 'running 2 Etherpad instances' effect. I'm indeed using Etherpad and when a shared link is opened it takes >4 seconds to load

15:44 <ocdtr_web> fossterer: Yeah, essentially when you open a document, you are starting that application's server. It's not too bad with Etherpad, but you can really see the effect if you try something like Rocket.Chat.

15:44 <ocdtr_web> There are some ideas for improving this further that haven't been implemented yet.

15:46 <fossterer> ocdtr_web: I've been using Sandstorm for a while now and the immediate obstruct I see to advocate this to anyone is performance. What are those ideas? Would you mind telling me if you are a core member of this project?

16:02 <ocdtr_web> I am not a core member of the project. Just someone who checks chat pretty frequently. :D

16:02 <ocdtr_web> Kenton wants to implement snappy start for one: https://github.com/google/snappy-start

16:24 <crab> that would be nice

16:29 <isd> kentonv: does snappy-start deal with vdso stuff at all? I'm thinking about weird bugs involving checking the time.

16:30 <isd> It does depend on the apps too though; it's really not too hard to write apps that start quickly, it's just that most pre-existing apps don't worry about it.

16:32 <isd> If you're on a high-latency connection you're also likely to run afoul of the fact that sandstorm's per-grain-per-session subdomain approach ruins DNS caching.

17:02 <crab> hmm, i'm sure that affects me too. but not to a large extent, as far as i can tell.

17:47 <fossterer> ocdtr_web: Thanks