Ping me with questions. I ran Gemfire under it and it was fine (actually I had to work with OSv guys on implementing multicast at the time ;-)).
The only restriction on OSv is no forking. It is, after all, a single image approach. That was a challenge fro Gemfire's gfsh tool, so I had to hack it to spin up OSv images as opposed to exec'ing jvms. What I'm really hoping to do is to get Yardstick to measure Geode and Ignite as-is but also via OSv. Let me know if anybody would be willing to collaborate on the project. Thanks, Roman. On Fri, Apr 24, 2015 at 2:54 PM, Konstantin Boudnik <[email protected]> wrote: > Shouldn't be no coding, as far as I remember my early experiments with it. > I will start playing with it and will keep the ticket updated on the findings. > > Cos > > On Fri, Apr 24, 2015 at 04:48PM, Dmitriy Setrakyan wrote: >> Cos, >> >> This definitely sounds very investing. Is there any coding involved here, >> or should be simple install-n-run? >> >> D. >> >> On Fri, Apr 24, 2015 at 4:26 PM, Konstantin Boudnik <[email protected]> wrote: >> >> > Guys, >> > >> > I don't know how many ppl here have heard about OSv [1] before. In short: >> > it >> > is a cloud-computing focused OS, running on a hyperviser. Unlike a >> > traditional >> > VM it has a tiny footprint and a miniscule startup time, hence adding 1-2 >> > seconds to the application bootstrap. Unlike Docker, it provides full >> > process isolation. Plus many other tangible benefits. >> > >> > I have filed https://issues.apache.org/jira/browse/IGNITE-811 to >> > experiment >> > with mix of Ignite and OSv, which I believe can provide us with even better >> > performance and deployment advantages, compared to what we already have in >> > this project. >> > >> > [1] https://en.wikipedia.org/wiki/OSv >> > >> > Would love to hear any ideas, feedback from your guys. >> > Cos >> > >> > >> >
