7.6.200 Performance 1

[crystalreporting]

Just thought I'd let everyone know, in case you were experiencing slow client response times since upgrading to 7.6.200. At one client, we've found that opening a Macola application (like OE Enter Orders) takes up to a minute. We've been able to reduce this to a more normal 5 to 10 seconds by disabling their real-time virus scan..

Peter Shirley

http://www.linkcorp.com

 

[Macoladownunder]

Hey Peter,

It looks like you hit the nail on the head with this one. We reported this problem to Exact the day after our upgrade to 7.6.200 in February. Although they have been actively looking at it for us, they don't believe it is a problem because they can't duplicate it on their end. Reading Tek-Tips, there are some performance issues with the new compiler.

We tried your suggestion and it seems to reduce retrieval time dramatically. I still have to get my head around turning off real time scanning - but that's on the to do list for next week.

Thanks mate!!!!!!

MacolaDownUnder
Aussies using Macola

 

[crystalreporting]

I'll let you call me 'mate' but only because I'm originally from New Zealand. Actually, we're doing some research on this problem at the moment - the virus software our client uses has the ability to omit folders and or individual files from the real time scan process, however try as we might, we could not pinpoint the files or folders to omit. Our next step is to install a DLL 'sniffer' so we can see what executables and DLL's are being loaded when a Macola application runs - hopefully we'd then be able to add them to the list of files to omit. Turning off the realtime scan (although tempting) is not an option.

Peter Shirley

http://www.linkcorp.com

 

[stravis]

I would suggest exempting all of the DLLs in the MacSQL\bin directory on your server. These dlls contain the actual application code the contains all of the business logic for the Macola application screens. These dlls were added to Macola just recently in the 7.6.200 build and any Macola screenset may open 1 or more of these dlls when you launch the screenset from Macola Progression (Workflow) Explorer. It used to be that a single *.lbr file was launched on the local machine for each module (AR, AP, etc..). These lbr files have been replaced with the much more numerous *.dll files in the bin directory on the server.

Scott Travis

http://www.infospring.net

 

[crystalreporting]

That would (and did) seem to make sense to me, but it didn't work - excluding the bin folder still made the apps. take a long time to load. There has to be something else 'Macola' related that it is scanning - we also tried the Macola/Shared folder on the local machine, but it didn't fix the problem either. I guess given that we can clearly prove that the real-time scan slows down the application load time, we should throw it back at Exact...

Peter Shirley

http://www.linkcorp.com

 

[MacolaHelp]

I've read a few other posts that indicate the cleanup utility really helps. Anyone care to comment on this? I sure would like to try it at a few sites if it really works with these bizarre errors in 7.6.200+.

 

[stravis]

Are you using Pervasive or Microsoft SQL on the backend? If you are using Pervasive I would suggest excluding all *.btr files. You might also want to try excluding all of the *.exe files in the Macola root directory on the server. You might also try the files in the MacSql\Msl directory on the server. As a final solution nothing quite works as well as trying to exclude everything Macola, see if you have positive results, and then try to determine what part of files related to Macola are causing the problem.

Scott Travis

http://www.infospring.net

 

[mystifying]

I may be a little late on this thread, but just in case someone else is dealing with speed issues with 7.6.200.5 as we were on some workstations, Macola suggested we go to Enterprise Manager and turn named pipes back on, and then also remove the alias. It did do the trick, but am not sure why or how.

 

[crystalreporting]

Named Pipes is SQL's 'preferred' method to connect to the SQL server database via the network - I've only used this method a couple of times, and only when I couldn't get TCPIP working. Strangely enough I've spoken with people at Macola who claim Macola will run faster with TCPIP than it will with named pipes. I suspect that what you are seeing is an improvement in performance simply because the SQL client is not having to resolve an IP address from the host name - in other words, I don't think it's related to the anti-virus 'realtime' scan problem that slows 7.6.200 down. As an aside, I haven't made it back to the client where this is a problem, so I haven't had a chance to further test the exclusion of files to be scanned.

Peter Shirley

http://www.linkcorp.com