loading leads during operations

[Op3r]

I have advised a client of mine to not load leads during operation. Its a 200 seats on a multi server setup. And at any given time at least 170 to 200 agents are logged in to the server.

The database is a dual quadcore, 16gb memory and 300+ SaS raid 10 hard drive.

I know we can still load leads like 5 to 10k during operations but how about more than that? They have at least a million leads on the system.

Now my main question is how do you insure the stability of the system while having the ability to load at least 100k leads during operation? Should I got with dual quadcore on i7? add more memory? add more processor?

[mflorell]

The problem is the locks to the table while the loading is going on. We have several large clients that load leads during operations, but never more than 10k at once.

How many do they want to load at once during production hours?

[Op3r]

that is the question.

Ill go ask.

but if we just load 10k leads at a time during operation, it wont affect much right?

[Op3r]

typically they load leads in 25k batches and receive about 50k to 200k daily so I imagine what ever any optimization Ill do will probably count to nothing if I dont delete old records.

I am thinking what if vicidial have the capability to just put all the inactive list id to another table when not being used then will just be put to active list when activated will probably help the performance.

[DarknessBBB]

I have advised a client of mine to not load leads during operation. Its a 200 seats on a multi server setup. And at any given time at least 170 to 200 agents are logged in to the server.

The database is a dual quadcore, 16gb memory and 300+ SaS raid 10 hard drive.

Hi Op3r, sorry for the OT, but, may you write down the HW configs of your servers? I really thank you very much!

[mflorell]

Putting lists into separate tables is an interesting idea, but would require quite a bit of reprogramming to make it happen.