gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2020-03-25	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2020-03-17	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2020-02-26	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2020-02-18	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2019-09-10	Start linting for unneeded dollar signs	Marcel Amirault
	Do not use dollar signs in shell codeblocks when no output is shown
2019-08-19	Link to GitLab Performance Monitoring	Thong Kuah

2019-01-08	Make unordered lists conform to styleguide	Evan Read
	- Also makes other minor Markdown fixes that were near the main fixes.
2018-12-20	Always load the metrics the last	Lin Jen-Shin
	Because this could potentially load a model and we shouldn't load models before all the patches we have in places.
2018-11-13	Resolve Markdown ordered lists not conforming to styleguide	Evan Read

2018-10-02	Remove Gitlab::Git::Repository#rugged and Gollum code	Alejandro Rodríguez
	Cleanup code, and refactor tests that still use Rugged. After this, there should be no Rugged code that access the instance's repositories on non-test environments. There is still some rugged code for other tasks like the repository import task, but since it doesn't access any repository storage path it can stay.
2017-03-01	Execute metrics initializer earlier	Adam Niedzielski
	This makes sure that Gitlab::Metrics::RackMiddleware is added before Gitlab::EtagCaching::Middleware.
2016-11-09	Add more highlighting to Instrumentation doc	Robert Speicher
	[ci skip]
2016-09-12	Document how to track custom events	Yorick Peterse
	Fixes gitlab-org/gitlab-ce#22070 [ci skip]
2016-06-17	Track method call times/counts as a single metric	Yorick Peterse
	Previously we'd create a separate Metric instance for every method call that would exceed the method call threshold. This is problematic because it doesn't provide us with information to accurately get the _total_ execution time of a particular method. For example, if the method "Foo#bar" was called 4 times with a runtime of ~10 milliseconds we'd end up with 4 different Metric instances. If we were to then get the average/95th percentile/etc of the timings this would be roughly 10 milliseconds. However, the _actual_ total time spent in this method would be around 40 milliseconds. To solve this problem we now create a single Metric instance per method. This Metric instance contains the _total_ real/CPU time and the call count for every instrumented method.
2016-06-14	Instrument private/protected methods	Paco Guzman
	By default instrumentation will instrument public, protected and private methods, because usually heavy work is done on private method or at least that’s what facts is showing
2016-06-14	Measure CPU time for instrumented methods	Paco Guzman

2016-05-05	Added documentation on how to instrument methods	Yorick Peterse
	[ci skip]
2016-04-11	Track call counts in Gitlab::Metrics.measure_block	Yorick Peterse

2016-04-11	Store block timings as transaction values	Yorick Peterse
	This makes it easier to query, simplifies the code, and makes it possible to figure out what transaction the data belongs to (simply because it's now stored _in_ the transaction). This new setup keeps track of both the real/wall time _and_ CPU time spent in a block, both measured using milliseconds (to keep all units the same).
2016-04-06	Added dev guide for measuring Ruby blocks	Yorick Peterse