Digital Workshop

I'm having serious problems with the use of the publications create by the Opus.

I worked a lot during the month and made the pub, but one part of the publication work begins with the brakes, loading CPU grows up to 100% and it is impossible to move the cursor. I use a list box and connection to the database. If you choose items in the list box, the first 8-10 time everything is fine, but then everything starts to brake. More and more. Then the publication becomes impossible to use and had to use emergency exit.

Give, please, what should I change the settings so the pub worked quickly and not slow down?

it sounds like you have an error in a script which causes the program to go into a loop, using more and more CPU until it hangs or runs out of resources.
It is impossible to say what is causing the problem without knowing a bit about the publication.
You can scatter Debug statements around the script to see if you can spot what's going wrong.

Hi sandyn

Thanks very much for your advice. I use a simple script output of data from DB. It worked excellent previously. But when I added a fields (its now total 9) with the conclusion of images and the date of such a problem.




Maybe the challenge the database query? Indeed, the brakes appear when I click mouse on the list box.

Anything that stops inside a 'for' loop will cause the loop to freeze.
This will happen if Opus is waiting for 'records.NextRecord()' to return data from the Record Set.
The result will be the pub will lock up.

Paul

Ignore me -- never read it properly.
I need coffee.

Paul

As Sandyn says, you could have errors somewhere. So that may involve quite a bit of work to find the source or sources of a condition causing problems.

Normally if you are using images on the page inside ImageObjects, it will take time to refresh or change image that is shown. I use an action that pre-loads resources on Page show. However, in your case it seems you are trying to manipulate a whole catalog of images in RAM? Of course... that's a lot of processing. I think it is Vista as part of the problem... Vista likes to keep track of things... like always indexing files. Also, lots of swap operations between disk and Ram is likely. You never say in your Profile what your system configuration is. And will your users have same capability.

In your DB query you retrieve all columns and all records. You can find ways to cut that down to only what is needed 'now'. Otherwise, once you have read from the Database into an array, you should not have to read again from the database... just operate on the array. However your Array contains "how many" images at one time?

It may be more efficient to make your SQL statements work to only retrieve the ONE or the few records needed SELECTIVELY.

Since you use a Page array-variable (?), you could also zero out the Array when not being used.
pr.length = 0 ; //then it will be empty


BTW, once you fill an Array with 200 rows by 8 columns, and then later you write to the Array again only 15 rows by 3 columns.... I think the Array will still contain much of the "old data" -- it only overwrites the elements where the new data exists and may not destroy the old values. (someone correct me if I am wrong here)

Cheers,
larry

added thought.

Since you are using Triggers and Standard actions, it would be a good idea to add an "End Query action" somewhere. I don't know 'where' is best.

( it might be better to "Open" the Database connection ONCE... separately from the Listbox selections actions. Then 'later', CLOSE the DB "ONCE". ... currently I think you are opening many connections to the DB??? )

Thanks to all.


Lar_123, this may be important, I try it, thank you.