lins_kun wrote:

>>
>> >> the server don't have problem if DB are smaller than 150MB.
>> >> when it size go upper 150 Mb the server performance go to wrong
>>
>
> No, i haven't idea what the problem is.
> CPU, HyperThreading and SMP can cause the problem?
> Disk, uhmmm i don't think because it is Raid5 UW SCSI III with disk
> 15.000 RPM
> The memory not go up

Have you looked at the system statistics?


With lots of users, classic can become disk bound because every
transaction start requires a read and write to the header page and every
commit reads and writes the most current transaction inventory page.
But I'd be surprised if 130 users got to that point unless they're
really bashing the database. And the problem would be relative to load,
not database size.


Regards,


Ann