ivom2gi

9 ms·

31.
Java 6 vs. Java 7 vs. Java 8 between 2013 – 2016 usage stats(plumbr.eu)
3 points by ivom2gi 11y ago|2 comments
32.
Web application performance report: 2016 edition(plumbr.eu)
1 points by ivom2gi 11y ago|0 comments
33.
Doubling the latency – 63% more users lost(plumbr.eu)
1 points by ivom2gi 11y ago|0 comments
34.
Example: leaking native memory from Java Virtual Machine(plumbr.eu)
1 points by ivom2gi 11y ago|0 comments
35.
Exposing Java memory contents during runtime: Plumbr way(plumbr.eu)
4 points by ivom2gi 11y ago|0 comments
36.
Memory leaks – fallacies and misconceptions(plumbr.eu)
1 points by ivom2gi 11y ago|0 comments
37.
How a change in logback conf resulted in double the JDBC traffic via Hibernate(plumbr.eu)
1 points by ivom2gi 11y ago|0 comments
38.
Java 9 will use G1 as default GC algorithm. Explaining the G1 in details(plumbr.eu)
2 points by ivom2gi 11y ago|0 comments
39.
Common performance pitfalls during connection pool usage(plumbr.eu)
2 points by ivom2gi 11y ago|0 comments
40.
Java Garbage Collection Handbook(plumbr.eu)
1 points by ivom2gi 11y ago|0 comments
41.
Weak, Soft and Phantom References: Impact on GC(plumbr.eu)
2 points by ivom2gi 11y ago|0 comments
42.
Most popular relational databases – data from 1,200+ deployments(plumbr.eu)
1 points by ivom2gi 11y ago|0 comments
43.
Show HN: Plumbr – linking slow HTTP queries to root cause in Java source code(plumbr.eu)
3 points by ivom2gi 11y ago|0 comments
44.
by ivom2gi 11y ago
It actually does remove a lot of hassle from developers. But with every abstraction, the complexity is not actually removed, just hidden. This means that in situations where the abstraction fails, you would need to still understand the hidd
45.
Promotion rate impact on garbage collected languages(plumbr.eu)
12 points by ivom2gi 11y ago|3 comments
46.
by ivom2gi 11y ago
The GC pauses locking entire JVM for several seconds are indeed a concern for many application classes, financial exchanges included. Exactly for this purpose even designated JVMs are built, Azul for example is providing a pauseless JVM whi
47.
Allocation rate impact for garbage collected languages(plumbr.eu)
2 points by ivom2gi 11y ago|4 comments
48.
Squeezing a data structure into bitset to reduce the size 100x(plumbr.eu)
1 points by ivom2gi 11y ago|0 comments
49.
Examples how caching can backfire on perfomance(plumbr.eu)
1 points by ivom2gi 11y ago|0 comments
50.
Garbage Collection explained in details(plumbr.eu)
1 points by ivom2gi 11y ago|0 comments
51.
Java GC logs made easy(plumbr.eu)
1 points by ivom2gi 11y ago|0 comments
52.
Introduction to how Garbage Collection really works(plumbr.eu)
5 points by ivom2gi 11y ago|0 comments
53.
Java versions used: statistics from 2013-2015(plumbr.eu)
1 points by ivom2gi 12y ago|0 comments
54.
Java random number generators – a way to introduce lock contention to your app(plumbr.eu)
1 points by ivom2gi 12y ago|0 comments
55.
What is wrong with troubleshooting tools: weaknesses analyzed(plumbr.eu)
1 points by ivom2gi 12y ago|0 comments
56.
Garbage Collection: Real Difference Between Minor GC, Major GC and Full GC(plumbr.eu)
1 points by ivom2gi 12y ago|0 comments
57.
How to define performance requirements(plumbr.eu)
1 points by ivom2gi 12y ago|0 comments
58.
Four ways to improve the performance of multi-threaded applications(plumbr.eu)
4 points by ivom2gi 12y ago|0 comments
59.
by ivom2gi 12y ago
Enterprise = company. And it does not have to translate to "large" necessarily.
60.
by ivom2gi 12y ago
I guess the tooling in this case is about as good as it gets - independent of the tools used, writing Java EE "by the spec" has traditionally been painful independent of the IDE used.

More ›