# k-Medoids node saturates all cpu cores at 100%

**URL:** <https://forum.knime.com/t/k-medoids-node-saturates-all-cpu-cores-at-100/9310>\
**Category:** KNIME Analytics Platform\
**Created:** [September 5, 2017, 5:06pm UTC](https://forum.knime.com/t/k-medoids-node-saturates-all-cpu-cores-at-100/9310 "2017-09-05T17:06:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![SOH979](https://forum-cdn.knime.com/user_avatar/forum.knime.com/soh979/32/2277_2.png) [@SOH979](https://forum.knime.com/u/SOH979)\
**Post date:** [September 5, 2017, 5:06pm UTC](https://forum.knime.com/t/k-medoids-node-saturates-all-cpu-cores-at-100/9310/1 "2017-09-05T17:06:02Z")

</div>

Latest Knime, Windows 10,&nbsp;on 6-core (12 virtual) i7 cpu; k-Medoids node saturates \*ALL\* cpu cores at 100%. (RAM usage only 16% physical RAM)

Other, concurrently running workflow speed reduced to a crawl;

Is this expected behaviour?

BTW, data is 30000 rows x 1000 columns & node chunk size is 5000.

---

<div class="post-metadata">

**Author:** ![Iris](https://forum-cdn.knime.com/user_avatar/forum.knime.com/iris/32/14_2.png) [@Iris](https://forum.knime.com/u/Iris)\
**Post date:** [September 8, 2017, 3:23pm UTC](https://forum.knime.com/t/k-medoids-node-saturates-all-cpu-cores-at-100/9310/2 "2017-09-08T15:23:47Z")

</div>

Hi,

actually, I would suppose this is a good thing. This means the node is optimally implemented and uses as much processing power as possible to give you a fast solution.

+ yes this will take sometime. Especially the number of columns will consume quite some time.

Best regards, Iris&nbsp;

---

<div class="post-metadata">

**Author:** ![system](https://forum-cdn.knime.com/uploads/default/original/1X/ab3ccf34482a0329361734a18199390177204f15.png) [@system](https://forum.knime.com/u/system)\
**Post date:** [June 23, 2023, 8:27pm UTC](https://forum.knime.com/t/k-medoids-node-saturates-all-cpu-cores-at-100/9310/3 "2023-06-23T20:27:20Z")

</div>


