vespa - An engine for low-latency computation over large data sets

	Commit message (Collapse)	Author	Age	Files	Lines
*	Update copyright	Jon Bratseth	2023-10-09	1	-1/+1
\|
*	Update Verizon Media copyright notices.	gjoranv	2021-10-07	1	-1/+1
\|
*	Replace deadlock avoidance with metrics	Håkon Hallingstad	2020-10-19	1	-0/+38
\|
*	Avoid metrics on reentry of lock	Håkon Hallingstad	2020-10-08	1	-18/+37
\|
*	Avoid even small double-counting of locked time	Håkon Hallingstad	2020-10-07	1	-7/+8
\|
*	Make richer latency stats	Håkon Hallingstad	2020-10-05	1	-38/+22
\| \| \| \| \| \| \| \| \|	Makes a LatencyStats which provides some useful metrics, best explained there and in LatencyMetrics. This includes latency metrics, the "QPS" (e.g. the number of acquire() per second), and load metrics. Unfortunately I had to move from atomics to synchronized to accomplish this, but I see no other way.
*	Move lock metrics to MetricsReporter	Håkon Hallingstad	2020-10-03	1	-0/+138
	Adds two new metrics: - The load of acquiring each lock path: The average number of threads waiting to acquire the lock within the last minute (or unit of time). Aka the lock queue (depth). - The load of the lock for each lock path: The average number of threads holding the lock within the last minute (or unit of time). This is always <= 1. Aka the lock utilization. Changes the LockCounters to LockMetrics, and exporting those once every minute through MetricReporter which is designed for this.