Diagnosing some serious performance issues

Anything beyond the basics in using the LiveCode language. Share your handlers, functions and magic here.

Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller

Post Reply
Alistair
Posts: 33
Joined: Mon Jun 23, 2008 6:45 am

Diagnosing some serious performance issues

Post by Alistair » Mon Oct 06, 2008 3:57 am

I have begun to run into some very serious performance issues.

I am working on a project that began life in Hypercard and that I have been converting to run in Revolution. It has some quite long scripts which have required conversion. After making very good progress without any noticeable performance problems I have suddenly hit some very serious issues. As an indication of what I mean, here are the times I have measured for some basic actions:

Open the stack - 2 min 40 sec
Display the drop down menubar menu 7 seconds
Go to the second card (using Go Next menu) 40 seconds
Go from second to third card (using Go Next menu) 40 seconds

Unfortunately I am not able to pinpoint at what stage these started to appear and therefore what changes I made that could have caused them.

Does anyone have any suggestions as to how to go about tracking down the problem?

I am working on an OXS version of Revolution Enterprise 3.0 on a current-generation 2.4 GHz Macbook Pro.

malte
Posts: 1098
Joined: Thu Feb 23, 2006 8:34 pm
Contact:

Post by malte » Mon Oct 06, 2008 8:12 am

Hi Alistair,

without seeing the stack, this will be hard to pin down.

A few questions: Is the hcAddressing of the stac = true?
Any openCard,preOpenCard,openStack,preOpenStack scripts that might cause this?
Any background groups in your stack?

If you start with a fresh stack, do you also see any performance issues?
Do you still have an elder Rev version handy, in which you could try if the problem is related to the engine version?

All the best,

Malte

Alistair
Posts: 33
Joined: Mon Jun 23, 2008 6:45 am

Post by Alistair » Mon Oct 06, 2008 8:53 am

Thanks, Malte. Those leads sound very promising. I need to check the implications of the hcAddressing setting particularly. This explains some behaviour that I could not understand. Whether it also explains the performance problem remains to be seen.

I have an openCard script that I need to check also.

There is a background group. I wasn't the developer of the original HC stack so I'm discovering potential issues as I go.

When I open a partially converted stack I don't experience performance issues, but then buttons on the card on which I'm working don't function as required. It is since I have begun altering scripts that the problem has emerged. I think that it is very likely that it is to do with referring to fields.

Thanks very much for these suggestions. They give me quite a deal of hope that I will track down the problem reasonably quickly

Post Reply