CPU Affinity
The CPUAffinityX=X is being set incorrectly after ISBOXER exports to INNERSPACE. This happens during a session. Potentially as a character is log in and out.
The XML output of ISBOXER was examined and the cpu affinity is set correctly.
Problem 1
The eqclient in the eqclient.ini sets the CPUAffinity0=0 initially. ISBOXER never removes the parameter so every eqclient-character.ini is getting assigned core 0.
Problem 2
After a period of time, the CPUAffinityX=X seems to get assigned multiple times and with multiple values. The following is an example:
CPUAffinity13=5
CPUAffinity17=1
CPUAffninty12=4
The CPU affinity has gone up to 18 and assigned to cores which don't exist.
I had exported from ISBOXER a number of times and the stability improved. As CPUAffinity was set to various values over time the stability of the system suffered. I'll post the ISBOXER output shortly but it doesn't seem to be the likely cause.
My guess is that the eqclient is setting the CPUAffinity.
I've made the eqclient-character.ini files read only and this has significantly increased the stability of the system. The INNERSPACE console shows the processors are assigned correctly. Basically, I'm assigning one character to one core.
The eqclient does crash and this could be one of the other likely causes for the CPUAffinity to be set incorrectly. I've noticed in the Everqeust forums there may be a memory leak problem causing the client to crash.
The system is an 8 core Opteron 6128
Operating System
MS Windows 7 Ultimate 64-bit
CPU
AMD Opteron 34 °C
Magny-Cours 45nm Technology
RAM
16.0GB Dual-Channel DDR3 @ 667MHz (9-9-9-24)
Motherboard
H8SGL (CPU 1)
Graphics
hp f2304 @ 1920x1200
ATI Radeon HD 5800 Series
LogMeIn Mirror Driver
Hard Drives
117GB INTEL SSDSA2M120G2GC ATA Device (SATA)
977GB Western Digital WDC WD1002FAEX-00Z3A0 ATA Device (SATA) 30 °C
Optical Drives
HP DVD Writer 1270d ATA Device
Audio
SB Live! 24-bit
The XML output of ISBOXER was examined and the cpu affinity is set correctly.
Problem 1
The eqclient in the eqclient.ini sets the CPUAffinity0=0 initially. ISBOXER never removes the parameter so every eqclient-character.ini is getting assigned core 0.
Problem 2
After a period of time, the CPUAffinityX=X seems to get assigned multiple times and with multiple values. The following is an example:
CPUAffinity13=5
CPUAffinity17=1
CPUAffninty12=4
The CPU affinity has gone up to 18 and assigned to cores which don't exist.
I had exported from ISBOXER a number of times and the stability improved. As CPUAffinity was set to various values over time the stability of the system suffered. I'll post the ISBOXER output shortly but it doesn't seem to be the likely cause.
My guess is that the eqclient is setting the CPUAffinity.
I've made the eqclient-character.ini files read only and this has significantly increased the stability of the system. The INNERSPACE console shows the processors are assigned correctly. Basically, I'm assigning one character to one core.
The eqclient does crash and this could be one of the other likely causes for the CPUAffinity to be set incorrectly. I've noticed in the Everqeust forums there may be a memory leak problem causing the client to crash.
The system is an 8 core Opteron 6128
Operating System
MS Windows 7 Ultimate 64-bit
CPU
AMD Opteron 34 °C
Magny-Cours 45nm Technology
RAM
16.0GB Dual-Channel DDR3 @ 667MHz (9-9-9-24)
Motherboard
H8SGL (CPU 1)
Graphics
hp f2304 @ 1920x1200
ATI Radeon HD 5800 Series
LogMeIn Mirror Driver
Hard Drives
117GB INTEL SSDSA2M120G2GC ATA Device (SATA)
977GB Western Digital WDC WD1002FAEX-00Z3A0 ATA Device (SATA) 30 °C
Optical Drives
HP DVD Writer 1270d ATA Device
Audio
SB Live! 24-bit