# MacOS RX580 Scissors Segment very slow **URL:** https://discourse.slicer.org/t/macos-rx580-scissors-segment-very-slow/27852 **Category:** Support **Created:** [February 16, 2023, 7:10am UTC](https://discourse.slicer.org/t/macos-rx580-scissors-segment-very-slow/27852 "2023-02-16T07:10:12Z") **Posts on this page:** 1 **Showing post:** 5

### Author: ![zyy](https://avatars.discourse-cdn.com/v4/letter/z/50afbb/32.png) [@zyy](https://discourse.slicer.org/u/zyy) #### Post date: [February 17, 2023, 1:39pm UTC](https://discourse.slicer.org/t/macos-rx580-scissors-segment-very-slow/27852/5 "2023-02-17T13:39:40Z")

I saw this issues > [@Performance issues on Mac M1?](https://discourse.slicer.org/t/performance-issues-on-mac-m1/22564/11): > > Thanks for reporting. There does seem to be some instability on macs with Apple chips. I have run some simple tests and things run fine, but we have seen [previous issues](https://github.com/pieper/SlicerParallelProcessing/commit/2cf7d7d61e7b17cc949cb8fd31acefe9e4de25a1) indicating that the on-the-fly run time code conversion is not the same as running on native hardware. So until Apple fixes their emulation layer or Slicer is ported to the new architecture there are likely to be edge cases that fail. I tested the basic flow described by @semredogan and got the crash report below basically i… and I test this film in macbook pro 16 m1pro(Slicer5.2.1) scissors operation is twice as fast as 13600kf in hackintosh. but slow too much than 13600kf in windows11(too quick to even measure), and do 3-6 times big scissors will crashed. m1pro in macos problem looked so same with 13600kf in hackintosh. m1pro also is big.LITTLE design,have 8 p-core,2 e-core. So I suspect big.LITTLE design is the reason If m1pro could fix this problem,please take intel 13gen cpu in hackintosh,thanks a lot. white mac is too expensive in memory and disk for medical image developer --- _[View the full topic](https://discourse.slicer.org/t/macos-rx580-scissors-segment-very-slow/27852)._