Last modified: 2013-12-30 18:59:05 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T60776, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 58776 - support for sqlite journal in memory
support for sqlite journal in memory
Status: NEW
Product: MediaWiki
Classification: Unclassified
Database (Other open bugs)
1.23.0
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: sqlite
  Show dependency treegraph
 
Reported: 2013-12-20 23:11 UTC by Antoine "hashar" Musso (WMF)
Modified: 2013-12-30 18:59 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Antoine "hashar" Musso (WMF) 2013-12-20 23:11:40 UTC
To be able to rollback transactions, sqlite write a journal file on disk which is kind of slow. When one doesn't care about dataloss (ex a dev wiki), it would be nice to have the journal held in memory and thus saving disk I/O.

Doc:
http://www.sqlite.org/pragma.html#pragma_journal_mode

Whenever a connection to a sqlite file is made, one can issue the command:

 pragma journal_mode=memory;


Should probably be yet another global variable such as $wgSqliteJournalMode
Comment 1 Max Semenik 2013-12-25 18:53:42 UTC
Mmm, so you're proposing a change analogous to downgrading MySQL from InnoDB to MyISAM?:P
Comment 2 Antoine "hashar" Musso (WMF) 2013-12-30 18:59:05 UTC
For testing purpose, we don't care about lost of data during transaction, at worth test will fail :-D  That is merely to speed up tests when being run against a sqlite backend.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links