We have a Windows 10 Server connected to 7 computers, all wired.  When one computer is doing a Mass Update using the Transfer>Inventory, it severely slows down any other computer that are accessing other databases like Invoice.

5 computers are using Windows 10, while 2 still have Windows 7.

Any ideas what I can do to reduce the lag?

Hi Ray,

I have attached a picture of what my Server is showing.

No.

The slowdowns only happen when someone is doing a mass update.  I'll send another picture if I can recreate the scenario.

This is what happens when I am doing mass updates and posting to inventory

cbislander wrote on Nov 8^th, 2022 at 3:40pm:


That is all possible with Mass Update on the engine. Things that aren't are things that affect layout elements, like Visibility(), ReadOnly(), etc, etc.

-Ray

I apologize as I am mistaken. It appears that currently all of the XResultSet commands are not allowed in Mass Update on the Server. I'm looking into why this is and to see if we can allow most of them, with the exception of the ones that reference the form, in a Mass Update on the Engine in a future update of Sesame.

But your current code can be rewritten to be faster.

One thing you can do to make it faster is currently you are calling @XResultSetNew() and @XResultSetClose() twice per record. What I would recommend doing is call the @XResultSetNew() calls in Global Code, set the returns to a Stat and use that in your code. Then at the bottom of your current code check if you are on the last record.

If @ResultSetCurrentPosition() = @ResultSetTotal() Then 

and inside the If Statement, close the XResultSets.

Then:

			XResultSetValue(vNewitem, "ITEMCODE0", vC1)
			XResultSetValue(vNewitem, "TRANSDATE0", vLE0 )
			XResultSetValue(vNewitem, "TRANSNUMBER00", vINVOICE)
			XResultSetValue(vNewitem, "TRANSSUBNUMBER0", vITEMNUM)
			XResultSetValue(vNewitem, "SRTOUT0", vSROUT)
			XResultSetValue(vNewitem, "SMTOUT0", vSMOUT)
			XResultSetValue(vNewitem, "ANTOUT0", vANOUT)
			XResultSetValue(vNewitem, "NGTOUT0", vNGOUT)
			XResultSetValue(vNewitem, "TOTALOUT0", vTOTALOUT )
		        XResultSetValue(vNewitem, "SALES", vLNET1) 

Can be written as

			XResultSetValue(vNewitem, "ITEMCODE0", vC1, "TRANSDATE0", vLE0, "TRANSNUMBER00", vINVOICE, "TRANSSUBNUMBER0", vITEMNUM, "SRTOUT0", vSROUT, "SMTOUT0", vSMOUT, "ANTOUT0", vANOUT, "NGTOUT0", vNGOUT, "TOTALOUT0", vTOTALOUT, "SALES", vLNET1) 

And the same thing can be done with the other set of XResultSetValue commands.

-Ray

cbislander wrote on Nov 16^th, 2022 at 12:49pm:


Looks good to me at a quick glance. Should speed it up quite a bit as that is 20 less calls per record to the server.

Another thing that would speed up everything would be to run a Linux Server instead of a Windows Server. Now I know that's not exactly a small change but Linux is just faster.

-Ray

I tried it but it didn't work.

The mass update should post to the Invent form and create record in the Activity Form.

The example below is a special order refund.  That part worked using the new way.

ASHLEY      D199-00      DINING BENCH      DIN      
N914063
06/27/2022      0      0      0      1      

In the Activity form, it did not create a record.

The old way does create a record.



The speed did not appear to be that much faster.  The update involved 72 records.