Arrival Overview too slow

(0) Share

Report

Posted on by mikefern

170

Hi all,

I need some assistance please. I already posted this before and was marked suggested answer already but after trying all that it did not resolve the issue.

I have an issue where the Arrival Overview screen is too slow. So slow, it is practically impossible to work with. What I have done so far...

1. Applied the Arrival Overview hotfix which claims it speeds up this screen significantly. That did not work.

2. I then reorganized/rebuild and reindexed all WMS and Inventory tables and that did not make a difference either.

I am out of options. I'm not sure what else can be done to speed this up when reading records or working with the menu in general.

It appears that this menu points to two WMS Arrival tables that are temp tables so I obviously can't rebuild those.

Is there anything else I can try to fix this?

Any help is greatly appreciated.

Thank you,

*This post is locked for comments

I have the same question (0)

All responses (13)

Answers (0)

Crispin John Augustine 37,081 on at

Like (0)

Report

Hi Mike,

Could you please elaborate, which particular process in the Arrival Overview is slow?

Is it new arrivals taking time to get updated in the form, or some function in the form itself?

Also, it would be helpful if you share the link to your previous post, so we can compare which options did not work for you earlier (and also to avoid duplicate entries)

Regards,

Crispin

Was this reply helpful? Yes No
mikefern 170 on at

Like (0)

Report

Hi,

Thanks for reply. Slow as in it takes about two minutes just to load open the main screen with the transactions. Navigating between records such as PO's or Transfer Orders is slow too. Also, simply trying to click on the checkbox to start an arrival takes forever. On the setup tab, I do have checkboxes on all transactions but it show not take this long to view all available arrivals. Impossible to work with.

Here is link to previous post...

community.dynamics.com/.../579423

Any suggestions are appreciated.

Thanks,

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi!

> two WMS Arrival tables that are temp tables

How much records in the tables?

Can you test speed if off fill the table?

Was this reply helpful? Yes No
mikefern 170 on at

Like (0)

Report

Hi,

The thing is those two WMSArrival temp tables don't appear in Management Studio or SQL Maintenance in AX in order to re-index/rebuild so I don't see them.

I have rebuild all other invent, purchase and WMS tables and did not impact it in any way. Still the same.

Was this reply helpful? Yes No
Guy Terry 28,924 Moderator on at

Like (0)

Report

Hi mikefern,

What version of AX do you have / CU? What hotfix did you install?

Are you setting Days forward/Days back? If you have multiple sites, can you use Restrict to site?

Was this reply helpful? Yes No
mikefern 170 on at

Like (0)

Report

Hi,

AX 2012 R2

Hotfix applied was KB2980464 which is for slow performance using Arrival Overview. I see it installed under the about menu as a hotfix so I know it installed.

If I set days back 300 or even 100, it takes forever to load. We only have one site so that would not apply.

Also,

What I just noticed that takes the longest, as in a few minutes to load, is PO's. Still slow if I display the rest but Purchase Orders take the longest time. I have just rebuild/re-indexed the purchase tables and still no luck.

Thanks,

Was this reply helpful? Yes No
Guy Terry 28,924 Moderator on at

Like (0)

Report

Are you really receiving Purchase orders which are 100 to 300 days late?!

If it were me, I'd be getting a techy to stick one of the performance tracing tools over it to see exactly what it is doing and what is taking a long time. Is that an option for you?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

>The thing is those two WMSArrival temp tables don't appear in Management Studio or SQL Maintenance in AX in order to re-index/rebuild so I don't see them.

Temp table are two types

https://msdn.microsoft.com/en-us/library/gg845661.aspx

https://msdn.microsoft.com/en-us/library/bb314749.aspx

And often work with them very slow (fill/order...)

So, it will be good if you look at how they are used

Is it standard form?

If yes, give form's name, please.

Was this reply helpful? Yes No
Crispin John Augustine 37,081 on at

Like (0)

Report

Hi Mike,

could you restrict your ranges to the smallest possible ones, and share approximately how many records appear in the Overview and Lines grid?

Regards,

Crispin

Was this reply helpful? Yes No
Vilmos Kintera 46,149 on at

Like (0)

Report
I would also chip in to Grigory's suggestion around temp tables, but rather from a database perspective. On the referred previous topic my blog does have a reference for the PFE recommendations, in which it talks about TempDB as well on your SQL Server instance.

It is possible that you have TempDB contention, which makes your reads/writes slow when you use the temporary database heavily. How many CPU cores (NUMA cores) do you have, and what is the number of TempDB data files that you are using on your SQL Server instance?

What do you get back if you run this on your SQL Server Management Studio for the instance where AX database is running on?

USE TempDB;
GO

SELECT DB_NAME(database_id) AS 'Database_Name' ,CASE WHEN file_id = 2 THEN 'Log' ELSE 'Data' END AS 'File_Type' ,((size_on_disk_bytes/1024)/1024.0) AS 'Size_On_Disk_in_MB' ,io_stall_read_ms / num_of_reads AS 'Avg_Read_Transfer_in_Ms' ,CASE WHEN file_id = 2 THEN CASE WHEN io_stall_read_ms / num_of_reads < 5 THEN 'Good' WHEN io_stall_read_ms / num_of_reads < 15 THEN 'Acceptable' ELSE 'Unacceptable' END ELSE CASE WHEN io_stall_read_ms / num_of_reads < 10 THEN 'Good' WHEN io_stall_read_ms / num_of_reads < 20 THEN 'Acceptable' ELSE 'Unacceptable' END END AS 'Average_Read_Performance' ,io_stall_write_ms / num_of_writes AS 'Avg_Write_Transfer_in_Ms' ,CASE WHEN file_id = 2 THEN CASE WHEN io_stall_write_ms / num_of_writes < 5 THEN 'Good' WHEN io_stall_write_ms / num_of_writes < 15 THEN 'Acceptable' ELSE 'Unacceptable' END ELSE CASE WHEN io_stall_write_ms / num_of_writes < 10 THEN 'Good' WHEN io_stall_write_ms / num_of_writes < 20 THEN 'Acceptable' ELSE 'Unacceptable' END END AS 'Average_Write_Performance' FROM sys.dm_io_virtual_file_stats(null,null) WHERE num_of_reads > 0 AND num_of_writes > 0 AND database_id = DB_ID('tempdb')

Was this reply helpful? Yes No