mirror of
https://github.com/ClickHouse/ClickHouse.git
synced 2024-11-18 05:32:52 +00:00
8623cb232c
* CLICKHOUSE-4063: less manual html @ index.md * CLICKHOUSE-4063: recommend markdown="1" in README.md * CLICKHOUSE-4003: manually purge custom.css for now * CLICKHOUSE-4064: expand <details> before any print (including to pdf) * CLICKHOUSE-3927: rearrange interfaces/formats.md a bit * CLICKHOUSE-3306: add few http headers * Remove copy-paste introduced in #3392 * Hopefully better chinese fonts #3392 * get rid of tabs @ custom.css * Apply comments and patch from #3384 * Add jdbc.md to ToC and some translation, though it still looks badly incomplete * minor punctuation * Add some backlinks to official website from mirrors that just blindly take markdown sources * Do not make fonts extra light * find . -name '*.md' -type f | xargs -I{} perl -pi -e 's//g' {} * find . -name '*.md' -type f | xargs -I{} perl -pi -e 's/ sql/g' {} * Remove outdated stuff from roadmap.md * Not so light font on front page too * Refactor Chinese formats.md to match recent changes in other languages
51 lines
4.2 KiB
Markdown
51 lines
4.2 KiB
Markdown
# Yandex.Metrica Use Case
|
|
|
|
ClickHouse was originally developed to power [Yandex.Metrica](https://metrica.yandex.com/), [the second largest web analytics platform in the world](http://w3techs.com/technologies/overview/traffic_analysis/all), and continues to be the core component of this system. With more than 13 trillion records in the database and more than 20 billion events daily, ClickHouse allows generating custom reports on the fly directly from non-aggregated data. This article briefly covers the goals of ClickHouse in the early stages of its development.
|
|
|
|
Yandex.Metrica builds customized reports on the fly based on hits and sessions, with arbitrary segments defined by the user. This often requires building complex aggregates, such as the number of unique users. New data for building a report is received in real time.
|
|
|
|
As of April 2014, Yandex.Metrica was tracking about 12 billion events (page views and clicks) daily. All these events must be stored in order to build custom reports. A single query may require scanning millions of rows within a few hundred milliseconds, or hundreds of millions of rows in just a few seconds.
|
|
|
|
## Usage in Yandex.Metrica and Other Yandex Services
|
|
|
|
ClickHouse is used for multiple purposes in Yandex.Metrica.
|
|
Its main task is to build reports in online mode using non-aggregated data. It uses a cluster of 374 servers, which store over 20.3 trillion rows in the database. The volume of compressed data, without counting duplication and replication, is about 2 PB. The volume of uncompressed data (in TSV format) would be approximately 17 PB.
|
|
|
|
ClickHouse is also used for:
|
|
|
|
- Storing data for Session Replay from Yandex.Metrica.
|
|
- Processing intermediate data.
|
|
- Building global reports with Analytics.
|
|
- Running queries for debugging the Yandex.Metrica engine.
|
|
- Analyzing logs from the API and the user interface.
|
|
|
|
ClickHouse has at least a dozen installations in other Yandex services: in search verticals, Market, Direct, business analytics, mobile development, AdFox, personal services, and others.
|
|
|
|
## Aggregated and Non-aggregated Data
|
|
|
|
There is a popular opinion that in order to effectively calculate statistics, you must aggregate data, since this reduces the volume of data.
|
|
|
|
But data aggregation is a very limited solution, for the following reasons:
|
|
|
|
- You must have a pre-defined list of reports the user will need.
|
|
- The user can't make custom reports.
|
|
- When aggregating a large quantity of keys, the volume of data is not reduced, and aggregation is useless.
|
|
- For a large number of reports, there are too many aggregation variations (combinatorial explosion).
|
|
- When aggregating keys with high cardinality (such as URLs), the volume of data is not reduced by much (less than twofold).
|
|
- For this reason, the volume of data with aggregation might grow instead of shrink.
|
|
- Users do not view all the reports we generate for them. A large portion of calculations are useless.
|
|
- The logical integrity of data may be violated for various aggregations.
|
|
|
|
If we do not aggregate anything and work with non-aggregated data, this might actually reduce the volume of calculations.
|
|
|
|
However, with aggregation, a significant part of the work is taken offline and completed relatively calmly. In contrast, online calculations require calculating as fast as possible, since the user is waiting for the result.
|
|
|
|
Yandex.Metrica has a specialized system for aggregating data called Metrage, which is used for the majority of reports.
|
|
Starting in 2009, Yandex.Metrica also used a specialized OLAP database for non-aggregated data called OLAPServer, which was previously used for the report builder.
|
|
OLAPServer worked well for non-aggregated data, but it had many restrictions that did not allow it to be used for all reports as desired. These included the lack of support for data types (only numbers), and the inability to incrementally update data in real-time (it could only be done by rewriting data daily). OLAPServer is not a DBMS, but a specialized DB.
|
|
|
|
To remove the limitations of OLAPServer and solve the problem of working with non-aggregated data for all reports, we developed the ClickHouse DBMS.
|
|
|
|
|
|
[Original article](https://clickhouse.yandex/docs/en/introduction/ya_metrika_task/) <!--hide-->
|