What is your caching setup (e.g. $wgMainCacheType and friends)? Caching
probably has more of an effect on read time than save time, but it will
also have an effect on save time, probably a significant one. If its just
one server, apcu (i.e. CACHE_ACCEL) is probably the easiest to setup.

There's a number of factors that can effect page save time. In many cases
it can depend on what the content of your page edits (e.g. If your edits
have lots of embedded images, 404 handling can result in significant
improvements).

The first step I would suggest would be to do profiling -
https://www.mediawiki.org/wiki/Manual:Profiling This will tell you what
part is being slow, and we can give more specific advice based on that

--
Brian

On Wed, Nov 28, 2018 at 2:17 PM Star Struck <[email protected]>
wrote:

> The server is just the localhost that I use for testing; it's Apache and
> MySQL running on Ubuntu 18.04 on an HP Elite 3.0ghz with 4GB of RAM
> <
> https://www.amazon.com/HP-Elite-Professional-Certified-Refurbished/dp/B0094JF1HA
> >.
> I haven't really figured out what kind of hardware or software I want to
> use for production, because I haven't done a lot of server administration
> (I've typically just used a VPS when I needed webhosting, but perhaps my
> needs now have expanded beyond that, because this is going to be a huge
> wiki, the same scale as Wikipedia; although my main concern at the moment
> is with making page saves, rather than page loads, more efficient, since I
> don't necessarily anticipate having a lot of visitors from the Internet
> reading the wiki, or else I'd be focusing more on stuff like caching; I
> mostly just want to set up a workable proof-of-concept for the moment.)
>
> I've heard that Wikimedia splits their enwiki database up among more than
> one server; is that how they're able to handle several page saves per
> second on the master?
>
> On Wed, Nov 28, 2018 at 8:19 AM Hershel Robinson <[email protected]>
> wrote:
>
> > > What's the best way to boost performance ...
> >
> > Depends on a myriad of factors, such as the OS, web server and
> > database and hardware etc.
> >
> > The simplest answer is to increase your hardware resources, meaning if
> > the site has one CPU, give it two. For anything more specific, we
> > would need more details about the server software and hardware.
> >
> > Hershel
> >
> _______________________________________________
> MediaWiki-l mailing list
> To unsubscribe, go to:
> https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>
_______________________________________________
MediaWiki-l mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l

Reply via email to