Jacek,
I completely agree with you for the central point of contact, it's much
simpler.
Nevertheless, in your previous mail you were mentioning informations given
by Monty :
>> Then apply the patch and retry, Monty mentioned some
>> extra switches (--force --force, etc), see his email, and try them
I'm not sure to have these informations about the extra switches your
talking about ? Do you know where i can get these, please ?
Thanks in advance for your answer.
Fabrice
On Thu, May 9, 2013 6:01 pm, Jacek Becla wrote:
> Fabrice
>
>
> I think it'd be better if the communication with Monty
> would go through one central point of contact (me).
>
> Let me know if you have any questions to him.
>
>
> thanks, Jacek
>
>
>
>
> On 05/09/2013 01:01 AM, Fabrice Jammes wrote:
>
>> Hello Jacek,
>>
>>
>> Thanks for these informations, I think we will have soon a machine with
>> enough disk space (around 8To) available, and I hope we will have
>> first results for the end next week.
>>
>> Do you know where it's possible to get Monty mail you're talking about
>> ?
>>
>>
>> Thanks,
>>
>>
>> Fabrice
>>
>>
>> On Tue, May 7, 2013 9:51 pm, Jacek Becla wrote:
>>
>>> Fabrice
>>>
>>>
>>>
>>>> Of course we can have a look a it.
>>>>
>>>>
>>>
>>> That is great!
>>>
>>>
>>>
>>>> Is there additional instructions for b) point ? If yes, could you
>>>> send it to us ?
>>>
>>> 1) Have a RunDeepForcedSource table ready. It should not be
>>> a production database, because we will be doing bad things to it.
>>>
>>> 2) Disable indexes (alter table RunDeepForcedSource disable index,
>>> than )
>>>
>>> 3) do not use that table through mysql while doing everything
>>> below. Either shut down mysqld, or run "flush cache" and don't touch
>>> that table
>>>
>>> 4) then test myisamchk, note that this is command line tool
>>>
>>>
>>>
>>> time /usr/local/mysql/bin/myisamchk -v -t <tmp_dir> --force
>>> -o
>>> --update-state
>>> -p
>>> --key_buffer_size=8M
>>> --sort_buffer_size= <~1/2 of your RAM available>
>>> --read_buffer_size=16M
>>> --write_buffer_size=16M
>>> <mysql data dir>/<db>/RunDeepForcedSource.MYI
>>>
>>>
>>>
>>>
>>> that will most likely fail, see
>>> https://dev.lsstcorp.org/trac/wiki/mysqlLargeTables
>>>
>>>
>>>
>>> Then apply the patch and retry, Monty mentioned some
>>> extra switches (--force --force, etc), see his email, and try them
>>>
>>> Please capture output (and the timing!) for each
>>> thing you run.
>>>
>>> it is probably better to use a machine that has reasonable amount of
>>> memory (say 32 or 64G), not insanely large amount of memory (on a
>>> machine with 256G ram I couldn't reproduce this problem).
>>>
>>>
>>> It is important that the <tmp dir> has enough space,
>>> at least the size of one copy of RunDeepForcedSource.* files.
>>>
>>> thanks Jacek
>>>
>>>
>>>
>>
>>
>
>
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1
|