Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate the cause of the FPE in the message/s estimate #194

Open
trink opened this issue Aug 20, 2019 · 2 comments
Open

Investigate the cause of the FPE in the message/s estimate #194

trink opened this issue Aug 20, 2019 · 2 comments

Comments

@trink
Copy link
Contributor

trink commented Aug 20, 2019

Investigate why the total time to number of messages ratio is so far off.
#192 (comment)

@trink
Copy link
Contributor Author

trink commented Aug 20, 2019

@hanego can you provide some information about your hardware/os/virtualization setup being run? I suspect there is a timer issue of some sort, thanks.

@hanego
Copy link

hanego commented Aug 21, 2019

@trink here are the infos you requested:

OS: Redhat 6.7

HW: Dell PowerEdge 630 & 640

Virtualization: none (baremetal & VTd disabled)

CPU: Xeon broadwell

Compiler EL 6 GCC 6.3.0 64-bit

$ lscpu

Architecture: x86_64

CPU op-mode(s): 32-bit, 64-bit

Byte Order: Little Endian

CPU(s): 16

On-line CPU(s) list: 0-15

Thread(s) per core: 1

Core(s) per socket: 8

Socket(s): 2

NUMA node(s): 2

Vendor ID: GenuineIntel

CPU family: 6

Model: 85

Model name: Intel(R) Xeon(R) Gold 6134 CPU @ 3.20GHz

Stepping: 4

CPU MHz: 3192.461

BogoMIPS: 6389.82

Virtualization: VT-x

L1d cache: 32K

L1i cache: 32K

L2 cache: 1024K

L3 cache: 25344K

NUMA node0 CPU(s): 0,2,4,6,8,10,12,14

NUMA node1 CPU(s): 1,3,5,7,9,11,13,15

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants