On 18/01/2013 11:34, Ewan MacMahon wrote:
>> -----Original Message-----
>> From: Testbed Support for GridPP member institutes [mailto:TB-
>> [log in to unmask]] On Behalf Of John Hill
>> Sent: 18 January 2013 11:20
>>
>>>
>>> 1) Is your SQL DB on the same machine? Ours is split so this may be a
>>> factor....
>>
>> The DB is on the same machine (which was fine under 1.8.3). This is a bare
>> metal (though quite old) server with plenty of memory (8GB).
>>
> Hmm. I'm not sure I'd call 8GB 'plenty of memory'; how big is the
> database in total?
About 14GB. 8GB memory was fine with DPM 1.8.3, so if it is inadequate
now then something significant has changed - and there's nothing in the
Release Notes highlighting the need for a larger machine for 1.8.4 or 1.8.5.
John
>
>>> 2) Maybe drop the requests tables in the DB? I know this can certainly
>>> have an affect on performance.
>>
>> I'll have a look at this.
>>
> If it hasn't been done at all it's well worth it, but I'd have
> thought you'd have DPM REQCLEAN in /etc/shift.conf?
>
>>
>> I was expecting EMI-1 to EMI-2 to be relatively painless for the DPM head
>> node. I should really know better by now.
>>
> Did the higher load definitely kick in with the upgrade and not
> earlier in the week when the problem with ATLAS pd2p data
> distribution was fixed?
>
> Ewan
>
|