we had a significant network performance slowdown back to 1 week ago which initially we thought was caused by server performance.
After tuning up a few servers, the situation seems to be improved but the system response is still notably slow.
Eventually we got to look at the firewall (Cisco ASA which replaced the pix firewall a week ago, the CRC error seems to be introduced at that time).
I did a ping from the Cisco ASA firewall and observed packet loss, the network guy later discovered CRC errors using show interface command (I did same thing but didn't notice the CRC error!) which apparantly is the root caused of the problem.
I have to admit though, by looking at the server side of things, we did discover a few performance bottleneck and improved the application performance. I guess this can also be noticed when the netowrk is back to normal.
Good lesson.
Subscribe to:
Post Comments (Atom)
Elevating LLM Deployment with FastAPI and React: A Step-By-Step Guide
In a previous exploration , I delved into creating a Retrieval-Augmented-Generation (RAG) demo, utilising Google’s gemma model, Hugging ...
-
Error 15401: Windows NT user or group '%s' not found. Check the name again. SELECT name FROM syslogins WHERE sid = SUSER_SID ('Y...
-
Finally, it is time. E4SE 811 and eBackoffice 736 will replace our current 810b/735a environment after staying so many years. Just got the n...
-
start /wait D:\Servers\setup.exe /qn VS=[VIRTUALSERVER] INSTANCENAME=[MSSQLSERVER] REINSTALL=SQL_Engine REBUILDDATABASE=1 ADMINPASSWORD=[CUR...
No comments:
Post a Comment