# Point list performance is very slow with large point list

**URL:** <https://discourse.slicer.org/t/point-list-performance-is-very-slow-with-large-point-list/23591>\
**Category:** Support\
**Tags:** markups\
**Created:** [May 25, 2022, 8:45pm UTC](https://discourse.slicer.org/t/point-list-performance-is-very-slow-with-large-point-list/23591 "2022-05-25T20:45:02Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![muratmaga](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/muratmaga/32/3622_2.png) [@muratmaga](https://discourse.slicer.org/u/muratmaga)\
**Post date:** [May 25, 2022, 8:45pm UTC](https://discourse.slicer.org/t/point-list-performance-is-very-slow-with-large-point-list/23591/1 "2022-05-25T20:45:02Z")

</div>

I am having quite a bit of slowdown with large number of points (500+)? Interactions are very slow, selection and any operations such as our MarkupsEditor, brings Slicer to almost stop. This is with the latest stable, both on Windows and Linux.

---

<div class="post-metadata">

**Author:** ![hherhold](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/hherhold/32/12199_2.png) [@hherhold](https://discourse.slicer.org/u/hherhold)\
**Post date:** [May 25, 2022, 8:51pm UTC](https://discourse.slicer.org/t/point-list-performance-is-very-slow-with-large-point-list/23591/2 "2022-05-25T20:51:48Z")

</div>

Try hiding the list of points. I posted about this a while back, can’t find the post now because I’m on my phone. Basically the list gets updated on mouse movements, or something like that.

---

<div class="post-metadata">

**Author:** ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)\
**Post date:** [May 25, 2022, 8:53pm UTC](https://discourse.slicer.org/t/point-list-performance-is-very-slow-with-large-point-list/23591/3 "2022-05-25T20:53:09Z")

</div>

Which version of Slicer are you using? There was a performance improvement committed recently which is available in latest Slicer preview. It is not present in current Slicer 5.0.2 stable.

> <https://github.com/Slicer/Slicer/issues/6379>
>
> Adding new markup control points is very slow if Markups module is active and co…ntrol points table is visible.
> 
> See user error report at https://discourse.slicer.org/t/adding-points-to-point-list-markup-becomes-progressively-slower/23419/4
> 
> \## Steps to reproduce
> 
> \- Create a \`Point list\` markup
> \- Add 100 control points
> \- Add one more control point - it takes a fraction of a second
> \- Go to Markups module, open Control points section
> \- Add one more control point - it takes several seconds
> 
> \## Expected behavior
> 
> Adding a control point should only take a fraction of a second.
> 
> \## Environment
> \- Slicer version: Slicer-5.1.0-2022-05-08
> \- Operating system: Windows10

---

<div class="post-metadata">

**Author:** ![muratmaga](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/muratmaga/32/3622_2.png) [@muratmaga](https://discourse.slicer.org/u/muratmaga)\
**Post date:** [May 25, 2022, 8:53pm UTC](https://discourse.slicer.org/t/point-list-performance-is-very-slow-with-large-point-list/23591/4 "2022-05-25T20:53:54Z")

</div>

> [@jamesobutler](#):
>
> Which version of Slicer are you using? There was a performance improvement committed recently which is available in latest Slicer preview. It is not present in current Slicer 5.0.2 stable.

OK. I am using the latest stable 5.0.2. Will this be backported to the stable?

---

<div class="post-metadata">

**Author:** ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)\
**Post date:** [May 25, 2022, 8:56pm UTC](https://discourse.slicer.org/t/point-list-performance-is-very-slow-with-large-point-list/23591/5 "2022-05-25T20:56:19Z")

</div>

Yes, see [this comment](https://github.com/Slicer/Slicer/issues/6379#issuecomment-1129059520) from @jcfr about the fix being a good candidate for 5.0.3. Backports have not been integrated into [GitHub - Slicer/Slicer at maintenance/5.0](https://github.com/Slicer/Slicer/tree/maintenance/5.0) yet, but they will be as part of the 5.0.3 release process.