e
>> was created with the latin1 charset, while the rest were in binary, which
>> made the use of indexes useless. "
>>
>> I've got tables with collations: binary (Innodb),
>> latin1_swedish_ci(MyIsam) , and a couple in utf8_bin (MyIsam) . How does
>> thi
ns: binary (Innodb),
> latin1_swedish_ci(MyIsam) , and a couple in utf8_bin (MyIsam) . How does
> this make the indexes not work?
>
> Sorry if any of these questions have been covered elsewhere. Feel free to
> tell me to google it, or toss a link my way, if you want.
>
>
&
the indexes not work?
Sorry if any of these questions have been covered elsewhere. Feel free to tell
me to google it, or toss a link my way, if you want.
thanks again!
Don Undeen
From: Thomas Fellows
To: don undeen
Cc: smw list
Sent: Mon, March 1, 2010 4:4
Hey -
Something you can try out that helped me out of a large smw-timeout issue
was actually really just related to a large MW issue, and MW's profiling
turned up the answer.
http://www.mediawiki.org/wiki/How_to_debug#Profiling
In my case, the Job Queue was what was killing my performance - temp
hi all,
I've got a semantic mediawiki installation with about
100,000 pages and growing, 236k rows in smw_ids, and 646k rows in
pagelinks
running on Windows Server 2008,
MediaWiki 1.13.5
PHP 5.3.1
MySQL 5.1.41
SMW 1.4.2
SMWHalo 1.4.5
I'm getting to the point where page loads are starting to be
