From: MB McAfee SR Update <support_reply@McAfee.com>
To: oleksandr.chernykh@playtech.com
Cc: linux-mm@kvack.org
Subject: RE: SR # <4-10997886031> Performance issues
Date: Wed, 30 Sep 2015 07:07:08 +0000 [thread overview]
Message-ID: <3e223314-c86d-4d0c-b71b-8096096de214@DNVEXAPP1N04.corpzone.internalzone.com> (raw)
Hello Oleksandr,
This is VMware. There are rcu stalls in the logs, which indicates that the VMs don't get enough CPU time assigned, the host might be overloaded or CPUs are overcommited. There are also network transmit timeouts in the logs, indicating the same.
The minimum memory for VMware is 16GB, please see the installation guide. The VMs only have 8GB assigned. Since there are load issues, I'd also suggest to assign more then the minimum CPU.
With kind regards,
Stefan Bluemel
Intel Security Technical Support
International: +1-888-847-8766
United Kingdom: 00800-6247-7463
Germany: 00800-1225-5624
Australia: +1-800-073-267
Web: http://www.mcafee.com
Web: http://mysupport.mcafee.com
Please respond only to support_reply@mcafee.com, keeping "SR # <4-XXXXXXXXX>" with your respective service request number in the subject line.
Keep up-to-date on your McAfee products! Subscribe to McAfee's NEW Support Notification Service (SNS) to get timely technical info.
Go to: http://my.mcafee.com/content/SNS_Subscription_Center
The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any review, dissemination, distribution or copying is strictly prohibited. If you have received this email message in error, please notify the sender by reply email and delete the message and any attachments.
-----------------
From: MFE Support Outbound Profile
Sent: 09/28/2015 07:30:17
To: oleksandr.chernykh@playtech.com
Cc: linux-mm@kvack.org
Subject: SR # <4-10997886031> Performance issues
Hello Oleksandr,
Thank you for contacting Intel Security technical support.
I have escalated this SR together with the provided data to our development team. I could not figure out why the directory node (node 3) was so overloaded.
I will keep you updated on their findings.
With kind regards,
Stefan Bluemel
Intel Security Technical Support
International: +1-888-847-8766
United Kingdom: 00800-6247-7463
Germany: 00800-1225-5624
Australia: +1-800-073-267
Web: http://www.mcafee.com
Web: http://mysupport.mcafee.com
Please respond only to support_reply@mcafee.com, keeping "SR # <4-XXXXXXXXX>" with your respective service request number in the subject line.
Keep up-to-date on your McAfee products! Subscribe to McAfee's NEW Support Notification Service (SNS) to get timely technical info.
Go to: http://my.mcafee.com/content/SNS_Subscription_Center
The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any review, dissemination, distribution or copying is strictly prohibited. If you have received this email message in error, please notify the sender by reply email and delete the message and any attachments.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2015-09-30 7:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 7:07 MB McAfee SR Update [this message]
2015-09-30 10:24 MB McAfee SR Update
2015-10-02 5:35 MB McAfee SR Update
2015-10-02 5:36 MB McAfee SR Update
2015-10-06 7:18 MB McAfee SR Update
2015-10-08 5:08 MB McAfee SR Update
2015-10-08 7:46 MB McAfee SR Update
2015-10-08 9:18 MB McAfee SR Update
2015-10-08 9:33 ` Oleksandr Chernykh
2015-10-08 9:41 MB McAfee SR Update
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3e223314-c86d-4d0c-b71b-8096096de214@DNVEXAPP1N04.corpzone.internalzone.com \
--to=support_reply@mcafee.com \
--cc=linux-mm@kvack.org \
--cc=oleksandr.chernykh@playtech.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox