TeaStore
are-we-fast-yet
TeaStore | are-we-fast-yet | |
---|---|---|
3 | 18 | |
115 | 315 | |
0.0% | - | |
4.7 | 8.8 | |
5 months ago | 3 months ago | |
Java | Java | |
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
TeaStore
- I have a webserver and a database running as pods, they're within the same subnet, but I think I'm having issues with connectivity and my webserver is shown an internal 500 error for the database. How can I narrow down this issue within my Kubernetes setup? I'm using KubeEdge, MicroK8s worked fine.
- stupid question, but can any application (Specifcally teastore) from github be used in argocd?
are-we-fast-yet
-
Boehm Garbage Collector
> Sure there's a small overhead to smart pointers
Not so small, and it has the potential to significantly speed down an application when not used wisely. Here are e.g. some measurements where the programmer used C++11 and did everything with smart pointers: https://github.com/smarr/are-we-fast-yet/issues/80#issuecomm.... There was a speed down between factor 2 and 10 compared with the C++98 implementation. Also remember that smart pointers create memory leaks when used with circular references, and there is an additional memory allocation involved with each smart pointer.
> Garbage collection has an overhead too of course
The Boehm GC is surprisingly efficient. See e.g. these measurements: https://github.com/rochus-keller/Oberon/blob/master/testcase.... The same benchmark suite as above is compared with different versions of Mono (using the generational GC) and the C code (using Boehm GC) generated with my Oberon compiler. The latter only is 20% slower than the native C++98 version, and still twice as fast as Mono 5.
-
A C++ version of the Are-we-fast-yet benchmark suite
See https://github.com/smarr/are-we-fast-yet/blob/master/docs/guidelines.md.
-
The Bitter Truth: Python 3.11 vs. Cython vs. C++ Performance for Simulations
That's a very interesting article, thanks. Interesting to note that Cython is only about twice as fast as Python 3.10 and only about 40% faster than Python 3.11.
The official Python site advertises a speedup of 25% from 3.10 to 3.11; in the article a speedup of 60% was measured. It therefore usually makes sense to measure different algorithms. Unfortunately there is no Python or C++ implementation yet for https://github.com/smarr/are-we-fast-yet.
- Comparing Language Implementations with Objects, Closures, and Arrays
- Are We Fast Yet? Comparing Language Implementations with Objects, Closures, and Arrays
-
.NET 6 vs. .NET 5: up to 40% speedup
> Software benchmarks are super subjective.
No, they are not, but they are just a measurement tool, not a source of absolute thruth. When I studied engineering at ETH we learned "Who measures measures rubbish!" ("Wer misst misst Mist!" in German). Every measurement has errors and being aware of these errors and coping with it is part of the engineering profession. The problem with programming language benchmarks is often that the goal is to win by all means; to compare as fairly and objectively as possible instead, there must be a set of suitable rules adhered to by all benchmark implementations. Such a set of rules is e.g. given for the Are-we-fast-yet suite (https://github.com/smarr/are-we-fast-yet).
-
Is CoreCLR that much faster than Mono?
I am aware of the various published test results where CoreCLR shows fantastic speed-ups compared to Mono, e.g. when calculating MD5 or SHA hash sums.
But my measurements based on the Are-we-fast-yet benchmark suite (see https://github.com/smarr/are-we-fast-yet and https://github.com/rochus-keller/Oberon/tree/master/testcases/Are-we-fast-yet) show a completely different picture. Here the difference between Mono and CoreCLR (both versions 3 and 5) is within +/- 10%, so nothing earth shattering.
Here are my measurement results:
https://github.com/rochus-keller/Oberon/blob/master/testcases/Are-we-fast-yet/Are-we-fast-yet_results_linux.pdf comparing the same benchmark on the same machine run under LuaJIT, Mono, Node.js and Crystal.
https://github.com/rochus-keller/Oberon/blob/master/testcases/Are-we-fast-yet/Are-we-fast-yet_results_windows.pdf comparing Mono, .Net 4 and CoreCLR 3 and 5 on the same machine.
Here are the assemblies of the Are-we-fast-yet benchmark suite used for the measurements, in case you want to reproduce my results: http://software.rochus-keller.ch/Are-we-fast-yet_CLI_2021-08-28.zip.
I was very surprised by the results. Perhaps it has to do with the fact that I measured on x86, or that the benchmark suite used includes somewhat larger (i.e. more representative) applications than just micro benchmarks.
What are your opinions? Do others have similar results?
-
Is CoreCLR really that much faster than Mono?
There is a good reason for this; have a look at e.g. https://github.com/smarr/are-we-fast-yet/blob/master/docs/guidelines.md.
-
Why most programming language performance comparisons are most likely wrong
Then apparently the SOM nbody program is taken as the basis of a new Java nbody program.
What are some alternatives?
jmeter-grpc-plugin - A JMeter plugin supports load test gRPC
gleam - ⭐️ A friendly language for building type-safe, scalable systems!
Jax-RS-Performance-Comparison - :zap: Performance Comparison of Jax-RS implementations and embedded containers
crystal - The Crystal Programming Language
rpc-bench - RPC Benchmark of gRPC, Aeron and KryoNet
fast-ruby - :dash: Writing Fast Ruby :heart_eyes: -- Collect Common Ruby idioms.
JankBenchX - Benchmark UI performance on Android devices.
PyCall.jl - Package to call Python functions from the Julia language
argocd-image-updater - Automatic container image update for Argo CD
Oberon - Oberon parser, code model & browser, compiler and IDE with debugger
quickperf - QuickPerf is a testing library for Java to quickly evaluate and improve some performance-related properties
Smalltalk - Parser, code model, interpreter and navigable browser for the original Xerox Smalltalk-80 v2 sources and virtual image file