Use the 2nd CPU core to calculate haloed lines

[Anonymous]

I wish ABS to be much faster so anything that can be calculated by the 2nd
CPU core should be done.

I wish you'd get a move on to support multi-core and not just for rendering
but to reduce the click wait click wait performance issues. Some of the
delays are massive 100% CPU show stoppers. Surely the time taken to
switching to a layout tab or refresh the haloed lines can be greatly
improved by utilising a 2nd core.

[Anonymous]

Agreed. I wonder if this will be programmed in the same time 64 bit
support will be added? It may make sense to do both at the same time
which is probably being held up by the continual delay of Vista. Just a
thought.

John wrote:
> I wish ABS to be much faster so anything that can be calculated by the 2nd
> CPU core should be done.
>
> I wish you'd get a move on to support multi-core and not just for rendering
> but to reduce the click wait click wait performance issues. Some of the
> delays are massive 100% CPU show stoppers. Surely the time taken to
> switching to a layout tab or refresh the haloed lines can be greatly
> improved by utilising a 2nd core.

[mdaniel]

It is intresting to read somthing related to delay's in ABS. We are trying to manipulate drawings 100meg plus and it gets to be quite fustrating at times. Do you know or have you been involved with any discussions on what the best hardware might be for ACAD use?

[dtiemeyer]

I've found that usually most of my users have more than 1 drawing/design to work on at a time. So if 1 drawing gets a long delay in ABS, I have them open a second instance of ABS, the start modifying their other files that need changing - the second instance of ABS will utilize the second virtual processor while your first command is still chugging away. I too would like better multi-processor support, but until that becomes a reality, making small workflow changes has helped us better deal with the delay times in ABS.