Wi imedia Foundation and the Wi imedia chapters Wi imedia Foundation logo Main article: Wi imedia Foundation Wi ipedia is hosted

and funded by the Wi imedia Foundation, a non-profit organiz ation which also operates Wi ipedia-related projects such as Wi tionary and Wi i boo s. The Wi imedia Foundation relies on public contributions and grants to fun d its mission.[203] The Wi imedia chapters, local associations of users and supp orters of the Wi imedia projects, also participate in the promotion, development , and funding of the project. Software and hardware See also: MediaWi i The operation of Wi ipedia depends on MediaWi i, a custom-made, free and open so urce wi i software platform written in PHP and built upon the MySQL database sys tem.[204] The software incorporates programming features such as a macro languag e, variables, a transclusion system for templates, and URL redirection. MediaWi i is licensed under the GNU General Public License and it is used by all Wi imed ia projects, as well as many other wi i projects. Originally, Wi ipedia ran on U seModWi i written in Perl by Clifford Adams (Phase I), which initially required CamelCase for article hyperlin s; the present double brac et style was incorpora ted later. Starting in January 2002 (Phase II), Wi ipedia began running on a PHP wi i engine with a MySQL database; this software was custom-made for Wi ipedia by Magnus Mans e. The Phase II software was repeatedly modified to accommodate t he exponentially increasing demand. In July 2002 (Phase III), Wi ipedia shifted to the third-generation software, MediaWi i, originally written by Lee Daniel Cr oc er. Several MediaWi i extensions are installed[205] to extend the functionali ty of the MediaWi i software. In April 2005 a Lucene extension[206][207] was add ed to MediaWi i's built-in search and Wi ipedia switched from MySQL to Lucene fo r searching. The site currently uses Lucene Search 2.1,[208] which is written in Java and based on Lucene library 2.3.[209] Diagram showing flow of data between Wi ipedia's servers. Twenty database server s tal to hundreds of Apache servers in the bac end; the Apache servers tal to fifty squids in the frontend. Overview of system architecture, December 2010. See server layout diagrams on Me ta-Wi i. Wi ipedia receives between 25,000 and 60,000 page requests per second, depending on time of day.[210] Page requests are first passed to a front-end layer of Squ id caching servers.[211] Further statistics are available based on a publicly av ailable 3-months Wi ipedia access trace.[212] Requests that cannot be served fro m the Squid cache are sent to load-balancing servers running the Linux Virtual S erver software, which in turn pass the request to one of the Apache web servers for page rendering from the database. The web servers deliver pages as requested , performing page rendering for all the language editions of Wi ipedia. To incre ase speed further, rendered pages are cached in a distributed memory cache until invalidated, allowing page rendering to be s ipped entirely for most common pag e accesses. Wi ipedia employed a single server until 2004, when the server setup was expande d into a distributed multitier architecture. In January 2005, the project ran on 39 dedicated servers in Florida. This configuration included a single master da tabase server running MySQL, multiple slave database servers, 21 web servers run ning the Apache HTTP Server, and seven Squid cache servers. Wi ipedia currently runs on dedicated clusters of Linux servers (mainly Ubuntu),[213][214] with a fe w OpenSolaris machines for ZFS. As of December 2009, there were 300 in Florida a nd 44 in Amsterdam.[215]