[
https://issues.apache.org/jira/browse/IGNITE-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16287609#comment-16287609
]
ASF GitHub Bot commented on IGNITE-7118:
----------------------------------------
GitHub user oignatenko opened a pull request:
https://github.com/apache/ignite/pull/3210
IGNITE-7118 performance measurement for distributed k-means clustering
- enabled benchmark after integration of necessary fix from master
-- verified with diffs overview, clean rebuild, trial execution of the
benchmarks and studying results
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7118
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3210.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3210
----
commit a782ee3f944d556686e8d0a68acb3f534e3ecb13
Author: Oleg Ignatenko <[email protected]>
Date: 2017-12-12T13:30:11Z
IGNITE-7118 performance measurement for distributed k-means clustering
- enabled benchmark after integration of necessary fix from master
-- verified with diffs overview, clean rebuild, trial execution of the
benchmarks and studying results
----
> performance measurement for distributed k-means clustering
> ----------------------------------------------------------
>
> Key: IGNITE-7118
> URL: https://issues.apache.org/jira/browse/IGNITE-7118
> Project: Ignite
> Issue Type: Bug
> Components: ml, yardstick
> Reporter: Oleg Ignatenko
> Assignee: Oleg Ignatenko
>
> We want to start tracking our performance to avoid performance degradation.
> Also we need some performance comparison with other ml libs.
> Initial draft for this benchmark was made per IGNITE-6123 (class
> {{IgniteKMeansDistributedClustererBenchmark}}) but it currently fails because
> of the implementation issues reported in IGNITE-6849 so it is excluded.
> Enable this benchmark and re-test it using codebase that has has corrected
> implementation.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
