Large Report Slow Loading

[[Sa...]]

Hello All!

I need a different way to make this report. I need 500 parts returned, but without the loading lag. I've found that my computer can handle the strain, but the engineers on the floor have been having issues with multiple minutes going by while this report boots up (before any data binding is selected) plus multiple minutes following the selection of a data binding.

Any ideas on how to accomplish this?

Let me know!!

Thanks 🙂
-Sam

Example Report.zip

[[Jo...]]

I've noticed that it takes a long time to pass data over to PiWeb, but excel output is instant. So in my case it isn't Calypso that is the bottleneck.

[[Da...]]

What are you trying to do? The reports is loading quickly but my guess would be that the fetching of data is slow. How many parts (in the inspection plan) do you check? How many sub parts do the parts have?

[[Sa...]]

Please sign in to view this quote.

We check anywhere from 5 to 500 parts. The inspection plan could have anywhere from 15 to 300 characteristics measured, along with sub categories as well.

I made new reports by increments for max amount of parts = 50, 100, 200, 500, so if an operator is looking for data on 34 parts, they can use the report made for 50 max instead of the 500. This has solved the issue temporarily.

The reports are all hard programmed, I went through and wrote out qdb.measurment(171,1) through qdb.measurement(171,500) for any data I wanted returned. I believe this is my issue, it is causing the report to sift through all that info, even if it doesn't have to/

The operators were attempting to run the 500 max report every time, loading unneeded data and slowing their computers.

[[La...]]

Consider using a measurement table with a characteristic table nested in it. It will expedite your results.

[[Sa...]]

Please sign in to view this quote.

I do have a report designed this way, it was what the engineers mainly used for a while. The only issue is they asked for an export option to excel, and with this technique you mention Laura, it forces us to export two separate files (one containing inc part numbers, the other with characteristics and measured values) and merge the two files together. It saves time with programming and loading, however we end up losing time with the post-piweb operations that we use the data for.

If you know of a way to export all of the data into one excel file using the mentioned technique please let me know, as this would be the best of both worlds!

Thanks for the response!

[[Sa...]]

Please sign in to view this quote.

Just to clarify. Characteristic table nested in a Measurement table?

I have mine set up oppositely: Measurement table within Characteristic table.

Care to share an example report that I can look over?