Zugg Software :: View topic - [3.04a] Slow CMUD Responses with Searching and Spreadsheet View Open

Beginner Joined: 22 Dec 2008 Posts: 21

So far, I am finding 3.04a much better than 2.37 other than these issues.
I think these are related issues, but they could be two different things (if two I can split it into two topics if needed).

System and map info:

I do the following:

Leaving the "Spreadsheet View" window open or iconified causes CMUD to respond very slowly and even quit responding for
several seconds before updating the map and terminal windows (I've seen it take as much as 10s before it responds, some are
quick, but most take 1-4s before the map and terminal windows actually updates).

Let me know what other information you need (and how to get it from CMUD).

Thanks,
-- Delgar

Posted: Mon Mar 09, 2009 8:00 am

I think it's already been said that the spreadsheet view wasn't optimized. In general Zugg starts looking at optimizations closer to the stabilization of a version.

Question did you compact your original map (MDB) before converting it? I'm not sure if Zugg does an automagic compact in the conversion process.

Typically speaking though, leaving things like the spreadsheet view and the package editor will slow down CMUD because of the transactional nature of the underlying DBs and the sheer processing overhead in keeping the views updated.

I did a quick test my with my spread sheet view and noticed a slight pause, but nothing major. Then again my map isn't 20 meg either.

Beginner Joined: 22 Dec 2008 Posts: 21

Yes, I compact my map DB on a regular basis since there are so many rooms on the mud and did so just before
moving to the beta version.

I understand that optimizations are left until late, but I wanted this noted in case it isn't an optimization issue.

I know this will be very low on the priority list (assuming it is an optimization issue) and so I don't expect a fix
any time soon, but the "find room" feature is only partially usable with the long delay opening and then very slow
response of the main window when the spreadsheet is left open.

Even with this issue, I am still finding v3.04a much better than 2.37 and will continue to use it.

If there is any additional information that is needed, please let me know.

-- Delgar

Posted: Mon Mar 09, 2009 5:15 pm

Never leave the Spreadsheet view open.

The Spreadsheet view is a very low-level database view of your map. It uses plain SQL statements to query the raw database on disk and does not use any of the in-memory "cache" that the rest of the mapper uses. As you guessed, the optimization for this is waiting until later in the beta process.

But even after the optimization, it will never be a good idea to leave the spreadsheet view open while playing. That will cause SQL updates to happen all of the time and will greatly slow down your playing.

Beginner Joined: 22 Dec 2008 Posts: 21

I usually don't (even though there isn't much impact on 2.37), but I was trying to work
around the 10s+ lag time in bringing up the spreadsheet view with the room search results.

Once the spreadsheet view is open, the searches go much faster (1-3s to display new results).
I figured if there was only the minor impact like on 2.37, I would just leave the spreadsheet
open when I was needing to do a bunch of quick searches back to back while moving around
the mud.

Magician Joined: 28 Jan 2007 Posts: 430

While Find Room feature is definitely handy, you could just as well script the search mechanism to do the same thing.

Consider the following: