flexmeasures VS FrameworkBenchmarks

Hi,

this is for everybody who is interested in clean tech, especially real-time automation within new energy systems.

We've been working on FlexMeasures for a while ― an energy management system (EMS) with a focus on using demand flexibility to its maximum potential.

We're running it in several pilots ourselves, but our aim is to speed up the energy transition across the world. Let's not re-invent the wheel (i.e. a software stack around time series and optimization) too many times. Wherever you are in the world, and whatever setting you might be looking at (energy-modern housing in the U.S., smart e-mobility in Africa, self-balancing microgrids in Indonesia, etc.), maybe some of you will like our approach.

We've decided that making it easy and clear for developers to build such energy solutions can bring the largest gains. The first step towards that goal was a permissive license (Apache 2.0). The latest step we took was a Docker image (we got a Docker-based tutorial here: https://flexmeasures.readthedocs.io/en/latest/tut/toy-exampl...).

You can see the code at https://github.com/FlexMeasures/flexmeasures

Since recently, FlexMeasures is a project within the Linux Energy Foundation (https://www.lfenergy.org/projects/flexmeasures/), which helps to establish a proper governance and quality standard.

Actually, upcoming Thursday is our next Technical Steering Committee meeting, and interested people are warmly invited:

Thursday, June 16 at 8:00 am US Pacific Time / 11:00 am US Eastern

I work on one building block of climate tech ― energy demand flexibility software. Useful in all kinds of settings, like industry or microgrids.

The collaborative aspect is that [our platform](https://github.com/FlexMeasures/flexmeasures) is open source, under a permissive license.

I'm trying to grow a startup on top of it, but the whole idea of doing impactful work is that it's being used to speed up the energy transition everywhere. Less re-inventing the wheel. If you are involved in any projects where energy demand flexibility should be unearthed, please consider using FlexMeasures ― with us or without us. Happy to chat.

Neat. Thanks for sharing!

Interestingly, may-minihttp is faring very well in the TechEmpower benchmark [1], for whatever those benchmarks are worth. The code is also surprisingly straightforward [2].

[1] https://www.techempower.com/benchmarks/

[2] https://github.com/TechEmpower/FrameworkBenchmarks/blob/mast...

ntex was formed after a schism in actix-web and Rust safety/unsafety, with ntex allowing more unsafe code for better performance.

ntex is at the top of the TechEmpower benchmarks, although those benchmarks are not apples-to-apples since each uses its own tricks: https://www.techempower.com/benchmarks/#hw=ph&test=fortune&s...

Ruby is slow. Very slow. How much you may ask? https://www.techempower.com/benchmarks/#hw=ph&test=fortune&s... fastest Ruby entry is at 272th place. Sure, top entries tend to have questionable benchmark-golfing implementations, but it gives you a good primer on the overhead imposed by Ruby.

It is also not early 00s anymore, when you pick an interpreted language, you are not getting "better productivity and tooling". In fact, most interpreted languages lag behind other major languages significantly in the form of JS/TS, Python and Ruby suffering from different woes when it comes to package management and publishing. I would say only TS/JS manages to stand apart with being tolerable, and Python sometimes too by a virtue of its popularity and the amount of information out there whenever you need to troubleshoot.

If you liked Go but felt it being a too verbose to your liking, give .NET a try. I am advocating for it here on HN mostly for fun but it is, in fact, highly underappreciated, considered unsexy and boring while it's anything but after a complete change of trajectory in the last 3-5 years. It is actually the* stack people secretly want but simply don't know about because it is bundled together with Java in the public perception.

*productive CLI tooling, high performance, works well in a really wide range of workloads from low to high level, by far the best ORM across all languages and back-end framework that is easier to work with than Node.JS while consuming 0.1x resources

Although that seems to have improved in recent years.

https://www.techempower.com/benchmarks/#hw=ph&test=json§...

RoR and whatever C++ based web backend there is count as a valid comparison in my book. But comparing the languages itself is maybe a bit off.

On a side note, you can actually compare their performance here if you’re really curious. But take it with a grain of salt since these are synthetic benchmarks.

https://www.techempower.com/benchmarks

Most benchmarks you'll find essentially have someone's thumb on the scale (intentionally or unintentionally). Most people won't know the different languages well enough to create comparable implementations and if you let different people create the implementations, cheating happens. The TechEmpower benchmarks aren't bad, but many implementations put their thumb on the scale (https://www.techempower.com/benchmarks). For example, a lot of the Go implementations avoid the GC by pre-allocating/reusing structs or allocate arrays knowing how big they need to be in advance (despite that being against the rules). At some point, it becomes "how many features have you turned off." Some Go http routers (like fasthttp and those built off it like Atreugo and Fiber) aren't actually correct and a lot of people in the Go community discourage their use, but they certainly top the benchmarks. Gin and Echo are usually the ones that are well-respected in the Go community.

There is certainly a lot of speculation in Techempower benchmarks and top entries can utilize questionable techniques like simply writing a byte array literal to output stream instead of constructing a response, or (in the past) DB query coalescing to work around inherent limitations of the DB in case of Fortunes or DB quries.

And yet, the fastest Ruby entry is at 274th place while Rails is at 427th.

https://www.techempower.com/benchmarks/#hw=ph&test=fortune&s...

oh what machine? with how many workers? doing what?

search for "node" on this page: https://www.techempower.com/benchmarks/#section=data-r21

JustJS would like a word https://www.techempower.com/benchmarks/#section=data-r20&tes...

In terms of RPS, this web service is more-or-less the fortunes benchmark in the techempower benchmarks, once the data hits the cache: https://www.techempower.com/benchmarks/#section=data-r21

Or, at least, they would be after applying optimizations to them.

In short, both of these would serve more rps than you will likely ever need on even the lowest end virtual machines. The underlying API provider will probably cut you off from querying them before you run out of RPS.