Sorry about calling the alarm too quickly.
Geek House Productions, Ltd.
Providing Unix & Internet Contracting and Consulting,
QA Testing, Technical Documentation, Systems Design & Implementation,
General Programming, E-commerce, Web & Mail Services since 1998
Address: 2459 E 41st Ave, Vancouver, BC V5R2W2
To defend against a bot, we must first distinguish between bots and legitimate users.
Maveric, being (1) a signed-in user (2) with sysop priviliges, is easily distinguishable from a bot. Don't get all insulted, mav, I mean that a computer program can easily distinguish you from a bot on the basis of the numbered points above.
Perhaps the edits-per-minute criterion could be applied to anonymous users.
"Watch this article" and "View article" are clearly wrong and need to be
changed. We have a definition for what we consider to be an article and that
doesn't include any namespaced pages and also doesn't include many pages in
the article:namespace. "Watch this page" is correct in all cases and should
be used. "View subject page" is also correct in all cases and should be used.
If this nomenclature we use is internally self-inconsistent then the
definitions we use for things become ambiguous and may become useless.
-- Daniel Mayer (aka mav)
Has anyone looked into making sure the MySQL server is configured
optimally? I'm not a MySQL expert, but I was reading over the MySQL
documentation and there are a number of parameters that can be adjusted
(like cache sizes).
There is also a MySQL command "SHOW STATUS" that might help to shed some
light on where the problems are. It reports things like number of cache
misses and number of times it had to wait for a table lock.
So, could someone with database access send me the results of running the
following two MySQL commands "SHOW STATUS" and "SHOW VARIABLES" (or post
the output to the list for everyone if they look interesting). I'll
examine them and report my findings.
Here is a link to what SHOW STATUS reports:
and some information on MySQL server optimizing:
As I said, I'm not an expert, but maybe there are some parameters that can
be tweaked (if they haven't been already) to improve performance in the
short term while a longer-term solution is worked on.
Thanks for the tweak.
From: Brion VIBBER [mailto:firstname.lastname@example.org]
Sent: Friday, September 20, 2002 3:12 PM
Subject: Re: [Wikitech-l] MySQL Configuration
When I switched the config file, I forgot to add in the max_connections
setting. Apparently the default is a mere 100, and I didn't notice that
it didn't get set in my-large.cnf. I bumped it back to our previous
setting of 250.
-- brion vibber (brion @ pobox.com)
Thanks to Steve Rawlinson for his analysis of tweakable factors slowing down Wikipedia access. I was especially intrigued by the "ed" value, for obvious personal reasons. ;-)
Anything performance tuning we can do *without* changing the table structure should be tried first.
Below is a report for the last week on how often the [[Chemstry]] page
took more than five seconds to load, according to my script.
Response times above five seconds can be considered as down time,
since the website feels so slow that users start to abandon it.
However, no actual down time was recorded this week. (Let's recall
how phase II worked, and bless the current blitz performance.)
The [[Chemistry]] page is rather short and simple, and should be
served as fast as the network can carry it. If the server spends
several seconds on each serving of this page, it will seem very busy.
The sooner it can get the page out of its hands, the better.
Mon, Nov 11, 18%
Tue, Nov 12, 8%
Wed, Nov 13, 10%
Thu, Nov 14, 2%
Fri, Nov 15, 4%
Sat, Nov 16, 2%
Sun, Nov 17, 4%
Mon, Nov 18, 6%
Tue, Nov 19, 7%
Around the clock (UTC time) over all days:
00:00 - 01:59 8% (7-9 pm EST, 4-6 pm PST)
02 6% (9-11 pm EST, 6-8 pm PST)
12 8% (7-9 am EST, 4-6 am PST)
14 6% (9-11 am EST, 6-8 am PST)
16 15% (11 am - 1 pm EST, 8-10 am PST)
18 11% (1-3 pm EST, 10-12 am PST)
20 9% (3-5 pm EST, 12-2 pm PST)
22:00 - 23:59 18% (5-7 pm EST, 2-4 pm PST)
Conclusion: Europeans should use Wikipedia in the morning.
At noon, the Americans wake up and the site gets bogged down.
Lars Aronsson (lars(a)aronsson.se)
Teknikringen 1e, SE-583 30 Linuxköping, Sweden
There seems to be some interest in creating a static HTML distribution
(dump) of Wikipedia, most notably it is requested on the
Wikipedia:Database_download page and in Feature Requests #596830 on
Sourceforge. This would allow people to download the Wikipedia for use
offline, for example from a CDROM.
So, I have started work and made my initial version (English only)
available online for anyone on this list to evaluate and test. I am
looking for feedback, suggestions, bug reports and general comments.
Please do not attempt to mirror the site as my server and bandwidth won't
be able to handle it. The site is only intended for developers to try and
give feedback. Once everyone is happy with it I will make .tar and .iso
packages available for distribution.
At the moment, the method I use to create the static HTML version is very
lengthy in terms of processing time and requires a number of manual step.
It takes my 1 GHz machine about 5 hours to generate all the pages.
Ideally, I'll have something more automated and efficient as time goes on.
My plan for how things would work is I will produce an updated static HTML
version every few months or significant milestones.
I'm not sure how to distribute this static HTML version when it's ready
for a public release. Currently it's about 500 Meg in size (that includes
everything). As I mentioned above I have limited server resources. For
distribution maybe it could be put on the Sourceforge download page, or on
the Wikipedia.org server somewhere (/tarballs)?
Finally, since I am new to Wikipedia and this list, please excuse me while
I learn how things work around here. I am open to criticism, suggestions
and discussion. I am looking forward to working with everyone on
Wikipedia and contributing where I can.
Some Technical Details (for those interested):
- English only (currently)
- uses "printable" pages, no top or side navigation bars
- added links to home, back, copyright and Wikipedia.org to bottom of all
pages (TODO: if a talk page exists a link should be added)
- pages are stored in directories based on first two characters of MD5
hash, same as image storage scheme
- includes all namespaces (talk, users, users_talk, wikipedia_talk, etc.)
- created a list with links to all the items in each namespace to allow
for basic searching of page titles
- redirects replaced with direct link to article
I've signed up for the technical list againand now I
find myself drowning in Wikipedia mailing lists... but
next week I should have a nice computer in Slovenia to
work with, so hopefully that will not be a problem.
Anyway, we now have a problem (bug) on the Esperanto
Wikipedia and I thought perhaps other people on the
list might have some ideas. Basically, Esperanto has
special non-ASCII characters that are often typed on
the Internet by using an x after the ASCII letter, but
they are usually displayed in Unicode.
We need to be able to allow our users to type in
x-system or Unicode and have the result be in Unicode.
We also need to allow the users to view the Esperanto
encyclopedia in x-system in case they are using an
older browser that does not support it. In the older
software, this worked perfectly. We also had an extra
link on the top which allowed the user to switch their
view simply from X-System to Unicode and back by
manually editing a user preference.
Is this possible simply by editing EoLanguage.php or
do will we need to edit other files as well? Which
one(s)? Also, it would help if Brion could give a
technical explanation of the problem here so perhaps
even I could try to help solve it soon. I would like
this to be fixed before I start the next wave of
I'm in the Czech Republic!! Mi estas en Cxehxio!!
Travel Plans: http://eo.wikipedia.com/wiki/Chuck_SMITH
My Webpage: http://amuzulo.babil.komputilo.com/
Gesendet von Yahoo! Mail - http://mail.yahoo.de
Möchten Sie mit einem Gruß antworten? http://grusskarten.yahoo.de