git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [spf:guess] Re: [spf:guess] Re: Git import of the recent full enwiki dump

From
Sam Vilain <sam@vilain.net>
Date
Apr 17, 2010, 03:34 UTC
Message-ID
<1271475292.3506.53.camel@denix>
In-Reply-To
<20100417015857.GD32053@post.servercare.de>
On Sat, 2010-04-17 at 03:58 +0200, Sebastian Bober wrote:
Show 10 quoted lines
> > Without good data set partitioning I don't think I see the above
> > workflow being as possible.  I was approaching the problem by first
> > trying to back a SQL RDBMS to git, eg MySQL or SQLite (postgres would be
> > nice, but probably much harder) - so I first set out by designing a
> > table store.  But the representation of the data is not important, just
> > the distributed version of it.
> 
> Yep, we had many ideas how to partition the data. All that was not tried
> up to now, because we had the hope to get it done the "straight" way.
> But that may not be possible.

I just don't think it's a practical aim or even useful. Who really wants the complete history of all wikipedia pages? Only a very few - libraries, national archives, and some collectors.

> We have tried checkpointing (even stopping/starting fast-import) every
> 10,000 - 100,000 commits. That does mitigate some speed and memory
> issues of fast-import. But in the end fast-import lost time at every
> restart / checkpoint.

One more thought - fast-import really does work better if you send it all the versions of a blob in sequence so that it can write out deltas the first time around.

Another advantage of the per-page partitioning is that they can checkpoint/gc independently, allowing for more parallelization of the job.

Show 6 quoted lines
> > Actually this raises the question - what is it that you are trying to
> > achieve with this wikipedia import?
> 
> Ultimately, having a distributed Wikipedia. Having the possibility to
> fork or branch Wikipedia, to have an inclusionist and exclusionist
> Wikipedia all in one.

This sounds like far too much fun for me to miss out on, now downloading enwiki-20100312-pages-meta-history.xml.7z :-) and I will give this a crack!

Sam
Previous: Sebastian BoberNext: Sebastian Bober
Message 8 of 12 in “Git import of the recent full enwiki dump”
  1. Richard HartmannApr 16, 2010
  2. Sverre RabbelierApr 17, 2010
  3. Sebastian BoberApr 17, 2010
  4. Shawn O. PearceApr 17, 2010
  5. Sebastian BoberApr 17, 2010
  6. Sam VilainApr 17, 2010
  7. Sebastian BoberApr 17, 2010
  8. Sam VilainApr 17, 2010
  9. Sebastian BoberApr 17, 2010
  10. Richard HartmannApr 17, 2010
  11. Shawn O. PearceApr 17, 2010
  12. Sebastian BoberApr 17, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.