Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

7.6.200 Performance Issues

Status
Not open for further replies.

Rob7

Programmer
Dec 12, 2001
152
US
I was wondering if anyone else had seen a significant degradation in performance after upgrading to 7.6.200. I just sat and timed the deletion of a routing that took 2 minutes and 50 seconds. Just closing the routing entry screen consistantly takes close to two minutes. Exact has suggested taking real time scan off of the client machines to see if that speeds up the response, but I don't see what that will prove. If it does speed it up, it doesn't matter. You cannot have a client machine not run real time scan from a security standpoint. Any ideas would be welcome.

Rob

Cytec Corporation
rbrown@cyteccorp.com
 
All of my pervasive sites have complained vociferously about performance on 7.6.200. SQL seems to be okay. I think it's just another example of QC not making an effort to optimize the code for btrieve.
 
I have no problem with 7.6.200.5, but I have no Pervasive sites on it either.

What has Exact Tech Support said about this issue?

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports
 
I guess I should have indicated that this was an MS SQL platform and a 40 user full ERP site. What Exact has said is that going from 7.6.100 to 7.6.200 replaced the 50 or so LBR files where the programs were originally called with 2500 or so .DLL in the BIN file. If your virus software is running real time scan, the system is scanning any .DLL that is called for the module and application. They suggested that removing the real time scan from the client machine might improve the response time. This might be, but it really does not help because I have to go right back to running the real time scan when the test is over. There is no way I would disable the real time scan long term from a security standpoint.

Rob

Cytec Corporation
rbrown@cyteccorp.com
 
If this was an upgrade from microfocus to Fujitsu, you may want to consider using the cleanup utility that is provided with the upgrade. Be sure to backup the full Macola root directory. I have run into this on upgrades, the cleanup usually helps or you may want to do a clean install and migrate. One other item to consider is scanning the workstation for spyware (spybot or adaware). Depending on the client surfing practices, these unwelcome guests can severely degrade performance on some workstations.

 
I would suggest testing what Macola suggests, this would at least validate that the problem is the real time scan and you don't need to keep it like this. If you determine everything works quicker with the real time scan turned off then perhaps you can define exclusions for your real time scan, so that it excludes all of the DLLs in the macsql\bin directory.

If transactions are still slow after running this test, then please let us know so that we try to determine the true problem.

Scott Travis
infoSpring, LLC.
 
I will be back out to this client in a few days and I will test the removal of the real time scan, and I will run the clean up utility. This was an upgrade from MicroFocus to Fujitsu, so that might be what the problem is.

Thanks for your input and I will let you know what I find out.

Rob

Cytec Corporation
rbrown@cyteccorp.com
 
We have had severe slowdown on customer account views in AR - some taking 30 seconds or more to come up. We are using SQL/7.6.200.5/50 users. There is also a problem with the deletion of order lines in OE Order entry. We have a compulsory tax on our order lines here in Australia. This seems to cause a 'focus' problem for our users and they can't get back to the lines until they completely exit the order and come back in. Unfortunately, this is a bigger problem for us - we process 1000 orders per day and have customers who change their minds. Exact have recognised the latter as a bug, but the AR views we are still trying to prove this is a problem. Other than that, we are fine. The cleanup utility did take care of some other minor problems.

MacolaDownUnder
Aussies using Macola
 
The customer account view problem is a problem with how Macola stores and retrieves GL Distributions. This problem is especially difficult when you have a high order volume. I would suggest staying away from this feature and using custom reporting or a custom application if you need to view distributions.

As for you other problem I might suggest that you develop a custom app to delete these order lines for the time being.

Scott Travis
infoSpring, LLC.
 
There is also known issues with 'focus' when moving between Macola screens (alt-tab or minimizing). I've definitely seen a slow-down in client performance since 7.6.200. I suspect that the Fujitsu version seems to be more sensitive to restrictive networks (hubs not switches etc.), so make sure you have a good network backbone in place.

Peter Shirley
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top