David Roberts 1500074cb2 [ML] Add method to find the established memory use for a job (elastic/x-pack-elasticsearch#2449) ...

"Established" memory use will be one of the building blocks for smarter node
allocation.

In order for a job to be considered to have established memory usage it must:
- Have generated at least 20 buckets of results
- Have generated at least one model size stats document
- Have low variability of model bytes in model size stats documents in the
  time period covered by the last 20 buckets, which is defined as having a
  coefficient of variation of no more than 0.1

Relates elastic/x-pack-elasticsearch#546

Original commit: elastic/x-pack-elasticsearch@5032eb01d8

2017-09-12 10:25:53 +01:00

..

bin/x-pack

Add x-pack-env.bat

2017-08-23 14:16:36 -04:00

bwc

Build: Add build metadata generation and usage to xpack (elastic/x-pack-elasticsearch#2368)

2017-08-28 14:03:02 -07:00

config/x-pack

Rename core plugin and transport dirs

2017-02-10 11:02:42 -08:00

keys

Rename core plugin and transport dirs

2017-02-10 11:02:42 -08:00

licenses

Revert "Use shaded rest client dependencies" (elastic/x-pack-elasticsearch#2352)

2017-08-25 14:13:16 -05:00

ml-cpp-snapshot

Allow build to directly run under JDK 9 (elastic/x-pack-elasticsearch#2320)

2017-08-22 14:46:37 +09:30

src

[ML] Add method to find the established memory use for a job (elastic/x-pack-elasticsearch#2449)

2017-09-12 10:25:53 +01:00

build.gradle

Build: Set xpack to require keystore

2017-08-24 14:09:07 -07:00