Serge,
Right. And all the issues you point out are compounded when you work in the
VM/Docker/JVM world. If overall memory consumption and garbage collection
are an issue in general, then carving up a VM to share a Linux distro among
multiple JVMs in their own Docker images for Spring Boot instance
Yes I understand what you mean, but in some ways the JVM needs big
improvements. The first one that comes to mind is getting rid of the
garbage collector because it causes so many difficult problems in
terms of predictability. One of the reasons I love Swift so much is
that it manages to do away wi
Serge,
Sure. Absolutely. What I meant is that part of the problem that Loom is
solving is that of system thread context switching from user to kerenel mode
and back.
Running the JVM in kernel mode in an unikernel eliminates that context
switch without the need for an extra construct.
But that'
Actually Project Loom is all about providing user mode threads to the
JVM, so no more context switches and large memory footprint. Their
objective is to be able to support millions of lightweights threads on
a JVM that could normally only handle thousands of threads.
Regards,
Serge...
On Wed, F
One thing I forgot to mention when I brought this up is how fast threading in
the JVM might be in a unikernel. Because the JVM/Karaf is running in a
single process in the kernel, thread switching would not involve the
laborious user mode to kernel mode switches that current thread switching
does.
Serge,
I hadn't heard of Loom. I'll have to look into that a bit more. Like
François, I think the unikernels with Karaf would be dynamite. There are a
number of different unikernel and rump kernel projects out there right now.
The one that seems ready to move is OSv but it also appears to be a bi
I was just looking at what Project Loom
(https://jaxenter.com/project-loom-trend-watch-jvm-ecosystem-147448.html)
could mean for the JDK. Imagine having Java Fibers available in Karaf
you could build a highly scalable microservices platform that
maximizes hardware usage like crazy. If this is paire
Hi Ranx,
I realy like your point about the overhead of running a JVM in a Docker
world ;)
I think Karaf is a very good alternative to reduce this overhead and all
the tooling provided by Karaf make it the perfect solution :)
"Server->hypervisor->microkernel->JVM->Karaf(!)"
Regards,
François Pa
This is a little dated but it means someone was taking a swing at this back
with Karaf 3.x. I did see where Onos has moved on to using Karaf 4.x
although I don't know if they are still using OSv. Being able to boot Karaf
into unikernel means start up would be fast, there's little attack surface,
an
JB,
Thanks for the feedback. I'll check out the blog and look at where you've
been going.
This is sort of on track for what I'm thinking about. One has to read
between the lines a bit because the example is using VirtualBox and Docker
but OSv is the microkernel being used. In reality, what I'd be
Hi Brad
I know multiple Karaf use cases:
- embedded (I know in trucks, in the ESA spatial station ;))
- on prem
- on cloud
About hypervisor/cloud/container, I did a blog about
Karaf/Docker/Kubernetes:
http://blog.nanthrax.net/?p=849
So, what are you looking for ? A dedicated hypervisor for Kara
11 matches
Mail list logo
