Marine Layer – LLVM C/C++ Cloud backed front-end(marinelayer.io)
marinelayer.io
Marine Layer – LLVM C/C++ Cloud backed front-end
http://marinelayer.io
6 comments
Oh wow, great site. What's the tech behind it?
I'm really glad you like. A good friend put it together.
The tech is powered by cloud functions.
The tech is powered by cloud functions.
Sweet dude. Does the performance improvements eventually plateau or does it scale well for larger projects?
It actually scales better the more source files you have.
The bottleneck currently is link job dependencies. LLVM is a good example of that, It has 2000 tasks to complete. It hits a point about 360 in where it has to link a tool that is used to generate code for a later stage.
The fastest build would be all source files with no linking. That could be done in about 30 seconds. Same would apply if you had 1k or 10k source files, 30 seconds.
I picked LLVM because it is the toughest benchmarks for this because I want real world use cases and expectations.
The demo shows an 8 core machine. On a 16 core machine it can build it in under 2 minutes. https://asciinema.org/a/214eea3mnjcn1jeiuu3s3qwso
The bottleneck currently is link job dependencies. LLVM is a good example of that, It has 2000 tasks to complete. It hits a point about 360 in where it has to link a tool that is used to generate code for a later stage.
The fastest build would be all source files with no linking. That could be done in about 30 seconds. Same would apply if you had 1k or 10k source files, 30 seconds.
I picked LLVM because it is the toughest benchmarks for this because I want real world use cases and expectations.
The demo shows an 8 core machine. On a 16 core machine it can build it in under 2 minutes. https://asciinema.org/a/214eea3mnjcn1jeiuu3s3qwso
interesting!
The demo video shows "configure" (which is usually not parallelized) also progressing much faster than the local system.
I wonder how one would deal with "trusting trust" in such a system.
I wonder how one would deal with "trusting trust" in such a system.
The cmake step (configure) was actually run by symlinking vanilla clang and then was swapped back before the make step. The asciicasts were manually made so you will notice one starts before the other so they are roughly the same. I do really like your attention to detail though :)
"trusting trust" is a very interesting topic for a cloud compiler for sure. Funnily enough I was at the llvm developer meetup this month getting feedback on this exact topic.
There are many approaches to this. The easiest gain here avoiding that is using this for built bots. You use this service to speed up PR approval and discover breakages much faster, then build locally for your final release version to share with anyone.
For companies that need to have control of their own service for that reason we can provide enterprise accounts where they use their own cloud provider.
In general we download prebuilt compiler toolchains every day and use them without knowing if they are compromised. I don't see this as any different and would take same steps with an important product that needs protection from that problem before making a release version.
"trusting trust" is a very interesting topic for a cloud compiler for sure. Funnily enough I was at the llvm developer meetup this month getting feedback on this exact topic.
There are many approaches to this. The easiest gain here avoiding that is using this for built bots. You use this service to speed up PR approval and discover breakages much faster, then build locally for your final release version to share with anyone.
For companies that need to have control of their own service for that reason we can provide enterprise accounts where they use their own cloud provider.
In general we download prebuilt compiler toolchains every day and use them without knowing if they are compromised. I don't see this as any different and would take same steps with an important product that needs protection from that problem before making a release version.