Page 1 of 1

sort hangs on long list

Posted: Mon Jan 26, 2009 5:41 am
by omer kircher
hi jussi:

i have just started using version 3.96r

i find that sorting is VERY much slower than version 3.96c even on a new machine that is 3 to 4 times as fast as the one i have been using until this week.

i use the sort a lot, so i hope you can fix this.

in the meantime, i intend to go back to 3.96c

omer

Posted: Mon Jan 26, 2009 7:55 am
by jussij
How long is a long list :?:

Could you see if the same problem exists in this 3.96s beta version: http://www.zeusedit.com/z300/ze32v396s-beta.zip

Cheers Jussi

slow sort in version 396r

Posted: Mon Jan 26, 2009 6:00 pm
by omer kircher
Hi Jussi:

In my first message, I shouldn't have said "hung". It just took so long I THOUGHT it was hung.

The length of the list i was sorting was about 12,700.

I got version 3.96s beta and it seems to be fine.

Thanks again!

Omer

Posted: Mon Jan 26, 2009 10:23 pm
by jussij
In my first message, I shouldn't have said "hung". It just took so long I THOUGHT it was hung.
One thing to remember is the sort operation is a fully undoable event so doing big sorts does put some demand on the OS for memory.

You can see this demand if you take your 12,700 line file and run a sort and re-sort several times. Each subsequent sort will take longer as the size of the internal undo buffer grows in size.

As a side, note, you can flush the undo buffer by making a call to the UndoFlush keyboard function or alternatively closing then re-opening the file ;)

Cheers Jussi

sorting

Posted: Thu Jan 29, 2009 9:07 pm
by omer kircher
Hi Jussi:

I know about "fully undoable" etc. but thanks!

One thing that is curious to me is: after a number of sorts, it takes a long time to close, even after the file has been saved. It seems like it would just be a matter of releasing the memory. I always wonder what is going on.

Omer

Posted: Thu Jan 29, 2009 11:40 pm
by jussij
It seems like it would just be a matter of releasing the memory. I always wonder what is going on.
That is pretty much all it is doing ;)

For example if you run a few big sorts on a file and then run the UndoFlush you will notice the same delay. Also once the flush is complete you should notice the sorted file will now close instantly.

I think the slowness also relates to the fact that these undo events are held in a stack and as such the flush has to pop the event off stack before it can delete it.

Cheers Jussi

PS: I just ran this simple test and noticed a small bug in that the hourglass is getting displayed ;)