- SAP Community
- Products and Technology
- Additional Q&A
- ST03N : bad Average GUI Time => How can we optimiz...
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
ST03N : bad Average GUI Time => How can we optimize ?
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 01-08-2009 12:41 PM
Hello guru's,
we have a performance problem.
Our SAP server is located in Europe and our Australian sites are experiencing bad Gui times.
The GUI time is the time used in the network and the local front end for these communications steps (not the time in the application server, however). The GUI time does not contain the front end network time.
1.
How can I proof to our network partner that the problem is caused by the WAN line ?
(a specific tool, other then niping)
They state there is a max 0,3sec latency on the line, we see average GUI times of 2 seconds for all Australian sites ...
2.
Could something else cause this high gui time ? (I have once read something about the number of menu items, but this should be ok) Anyone has another idea?
Thank you for your time !
Bud
Accepted Solutions (0)
Answers (4)
Answers (4)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Hans,
This is mostly happend when network is slow.
Thanks
Kiran.GVL
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
you can also try to choose the "WAN Mode" in the GUI connection.
That way you have less traffic between Server and Client.
Do you have special Transactions (maybe have a look at the Transaction Profile) that cause longer wait times?
kind regards
Peter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
check tcode :OS01 it is more easy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
>(a specific tool, other then niping)
Why don't you want to use niping. This utility is the perfect tool to check network problems on a wan line for SAP connections. I've used it successfully to prove latency problems on a VPN for SAP acsess.
Regards,
Olivier
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hans,
On one end of the WAN line, you start niping as a server.
At the other end, you use niping as a client. We wrote a script to test every minute for 24 hours and log the results.
All is explained here :
[Note 500235 - Network Diagnosis with NIPING|https://service.sap.com/sap/support/notes/500235]
Regards,
Olivier
- Maximize Results and Drive Sustainability in Fashion Retail with SAP and GK AIR Dynamic Pricing in CRM and CX Questions
- Receive and present a clear picture of your process analysis to your business executives in Technology Blogs by SAP
- What Will You Do With Your Extra Day This Leap Year? in Supply Chain Management Blogs by SAP
- Navigating ST03N: Unraveling the Significance of Historical Transaction Usage in SAP Implementation in Technology Q&A
- SAP Sustainability Footprint Management: Q4-23 Updates & Highlights in Technology Blogs by SAP
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.