* Update to mima 0.1.13
* Filters when checking v2.4.8 against older
* Filters when checking v2.4.9 against older
* Filters when checking v2.4.10 against older
* Filters when checking v2.4.11 against older
* Filters when checking v2.4.12 against older
* Filters when checking v2.4.14 against older
* Filters when checking master against older
* Remove not used filter
* Make decoding release the envelope so it doesn't leak memory
* Create two different configurations, Standard and RemoteInstrument
* Create Serilaizer and RemoteInstrument that doesn't allocate memory
Needed by Akka Streams. Old functions placed in akka.japi will be deprecated
in 2.4
(cherry picked from commit 99628f408295070848af6c23b1d722057069e660)
+act #17392 Include generated japi.function from akka-stream
* add boilerplate plugin
* make them Serializable to be able to grab line number for Java 8 lambdas
(cherry picked from commit d5950a13d2f123d2101d56f0a8a86a2097dda8e1)
+ enable parallel execution
+ exclude perf tests (TODO mark more as such)
+ uses sbt-dependency-graph plugin
+ implement dependency tracking for testing of only these
+ project which could have been affected by a given PR
* load sample builds from their definitions and replace library dependencies with project ones
* remove redefined sample build definitions
* test osgi sample by running a maven command
Note: This is NOT aimed to provide an micro-benchmarking solution.
The goal is to provide data for broad trend analysis. For techniques
that fight the inliner and other specialised techniques, refer to JMH.
+ custom console and graphite reporters
- had to be custom because it's not possible to add custom metric
types to the existing reporters
+ initial hdr.Histogram histogram() provider, see
http://latencyutils.github.io/LatencyUtils/
+ Not using timers provided by Metrics, instead use the above histogram
+ Added average Actor size measurement
+ Measuring the "blocking time" when an actor is created, before we fire
of the async part of this process; Measures in loop and will fluctuate
a lot. Times are in `us` -- System.nanoTime should provide good enough
resolution.
+ Measuring total actor creation time by using
`KnownOpsInTimespanTimer`, which given a known number of ops, in a
large amount of time, roughtly estimates time per one operation.
// Yes, we are aware of the possibility of GC pauses and other horrors
+ All classes are `private[akka]`, we should not encourage people to use
this yet
+ Counters use Java 8's `LongAdder`, which is metric's private;
The new trend in Java land will be copy paste-ing this class ;)
+ Metrics are logged to Graphite, so we can long-term analyse these
+ Reporters are configurable using typesafe-config
! I'm not very happy about how I work around Metrics not being too open
for adding additional custom metrics. Seems like a hack at places.
I will consider removing the Metrics dependency all together.
numbers
Example output:
```
-- KnownOpsInTimespanTimer-------------------------------------------
actor-creation.total.creating-100000-actors.Props|new-EmptyArgsActor|…||-same
ops = 100000
time = 1.969 s
ops/s = 50782.22
avg = 19.69 μs
-- AveragingGauge---------------------------------------------------
actor-creation.Props|new-EmptyArgsActor|…||-same.avg-mem-per-actor
avg = 439.67
```
These are visible on the grafana dashboard,
in order to be able to see on which commit
stats have been recorded.
It's enabled via: `-Dakka.sbt.graphite=true`
Resolves#15103
- move license and homepage into build definition
- enable sbt-license-report plugin to properly pick it up
- remove hand-coded XML (always a good idea)
- remove ls.implicity.ly plugin
- remove STM reference from README
