delayed customer information

[Op3r]

i am having this weird problem that the agent gets a call on their phone but sometimes the customer information gets to be displayed in about 3 to 5 seconds.

Im using 2.0.4rc4

the loadavg are low here's the load of the mysql server

load average: 0.83, 0.50, 0.29 mysqld 5.0.22 up 7 day(s), 23:53 hrs
25 threads: 1 running, 6 cached. Queries/slow: 136.1M/0 Cache Hit: 99.69%
Opened tables: 0 RRN: 11.5K TLW: 174.7K SFJ: 0 SMP: 0 QPS: 553

ID USER HOST DB TIME COMMAND STATE INFO
5871771 cron localhost Query show


any ideas?

[mflorell]

What are the specs on the agent stations? (CPU/RAM/OperatingSystem)

[Op3r]

a p4 1.6 with 256mb ram with windows 2000 as OS.

Im using pap2 for their phone btw.

[Op3r]

does that kind of the problem is on the agent side now? Not on the servers anymore?


I dont see any errors on mtop

Im using core2quad with 4gb of memory with 300 gb sata on the server. The load is ok. It is a multi server set up.

[mflorell]

This can be a networking problem, a server load problem, or an agent side problem.

Is there and anti-virus running on the agent stations?

What browser are the agent stations using?

[Op3r]

I think they are running antivirus. I should probably remove it.

and they are using firefox 3

[mflorell]

Since you are using Firefox, be sure that you have automatic updates disabled. When it checks for updates Firefox will actually halt Javascripts running on the browser without any kind of warning.

[Op3r]

I still experience it even if the anti virus and firefox automatic update is disabled

here's my my.cnf

[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
# Default to using old password format for compatibility with mysql 3.x
# clients (those using the mysqlclient10 compatibility package).
old_passwords=1
skip-name-resolve
skip-host-cache
# addon
port = 3306
socket = /var/lib/mysql/mysql.sock
skip-locking
key_buffer = 384M
max_allowed_packet = 1M
table_cache = 512
sort_buffer_size = 2M
read_buffer_size = 2M
read_rnd_buffer_size = 8M
myisam_sort_buffer_size = 64M
thread_cache_size = 8
query_cache_size = 32M
# Try number of CPU's*2 for thread_concurrency
thread_concurrency = 8


[mysql.server]
user=mysql
basedir=/var/lib

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

[isamchk]
key_buffer = 256M
sort_buffer_size = 256M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer = 256M
sort_buffer_size = 256M
read_buffer = 2M
write_buffer = 2M

[client]
#password = your_password
port = 3306
socket = /var/lib/mysql/mysql.sock


Still at lost why I experience it though.

[mflorell]

what kind of network switches are used at this location?

How many network hops is it from the agent computers to the database and web servers?

[Op3r]

We are using 3com core switch 55 something and 3com managed switches.

One hop going to the dbase and web server.

I dont see any packetloss from the agent pc going to the server though.

One more thing is it possible for agents to do something to create this kind of scenario?

[mflorell]

How often does this happen?

[Op3r]

sometimes it is random, 1 agent at a time then it will gradually affect others too.

[mflorell]

what did you use as a base for my.cnf?

[Op3r]

huge-my.cnf

[mflorell]

On how many calls will an agent have the information delayed in one day on average?