blocks|key|1216290|text|MySQL支持名为"MEMORY“的存储引擎，您可以在数据库配置(settings.py)中对其进行如下配置：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1216291|++++'USER':+'root',++++++++++++++++++++++#+Not+used+with+sqlite3.
++++'PASSWORD':+'',++++++++++++++++++#+Not+used+with+sqlite3.
++++'OPTIONS':+{
++++++++"init_command":+"SET+storage_engine=MEMORY",
++++}|code-block|syntax|javascript|1216292|请注意，内存存储引擎不支持blob+/+text列，因此如果您使用的是django.db.models.TextField，这将不适用于您。|1216293|entityMap^0|X|B|0|0|Z|Q|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

MySQL supports a storage engine called "MEMORY", which you can configure in your database config (<code>settings.py</code>) as such:

<pre><code> 'USER': 'root', # Not used with sqlite3.
 'PASSWORD': '', # Not used with sqlite3.
 'OPTIONS': {
 "init_command": "SET storage_engine=MEMORY",
 }
</code></pre>

Note that the MEMORY storage engine doesn't support blob / text columns, so if you're using <code>django.db.models.TextField</code> this won't work for you.

blocks|key|1216366|text|我不能回答你的主要问题，但你可以做一些事情来加快速度。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1216367|首先，确保您的MySQL数据库设置为使用InnoDB。然后，它可以在每次测试之前使用事务回滚数据库的状态，这在我的经验中导致了巨大的加速。您可以在settings.py中传递数据库初始化命令(Django1.2语法)：|1216368|DATABASES+=+{
++++'default':+{
++++++++++++'ENGINE':'django.db.backends.mysql',
++++++++++++'HOST':'localhost',
++++++++++++'NAME':'mydb',
++++++++++++'USER':'whoever',
++++++++++++'PASSWORD':'whatever',
++++++++++++'OPTIONS':{"init_command":+"SET+storage_engine=INNODB"+}+
++++++++}
++++}|code-block|syntax|javascript|1216369|其次，您不需要每次都运行South迁移。在您的settings.py中设置SOUTH_TESTS_MIGRATE+=+False，将使用普通同步数据库创建数据库，这将比运行所有历史迁移快得多。|offset|length|style|CODE|1216370|entityMap^0|0|0|0|11|R|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@$K|U|L|V|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I can't answer your main question, but there are a couple of things that you can do to speed things up.

Firstly, make sure that your MySQL database is set up to use InnoDB. Then it can use transactions to rollback the state of the db before each test, which in my experience has led to a massive speed-up. You can pass a database init command in your settings.py (Django 1.2 syntax):

<pre><code>DATABASES = {
 'default': {
 'ENGINE':'django.db.backends.mysql',
 'HOST':'localhost',
 'NAME':'mydb',
 'USER':'whoever',
 'PASSWORD':'whatever',
 'OPTIONS':{"init_command": "SET storage_engine=INNODB" } 
 }
 }
</code></pre>

Secondly, you don't need to run the South migrations each time. Set <code>SOUTH_TESTS_MIGRATE = False</code> in your settings.py and the database will be created with plain syncdb, which will be much quicker than running through all the historic migrations.

blocks|key|1002169|text|如果在运行测试时将数据库引擎设置为sqlite3，则返回Django+will+use+a+in-memory+database。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1002170|运行测试时，我在settings.py中使用如下代码将引擎设置为sqlite：|style|CODE|1002171|if+'test'+in+sys.argv:
++++DATABASE_ENGINE+=+'sqlite3'|code-block|syntax|javascript|1002172|或者在Django+1.2中：|1002173|if+'test'+in+sys.argv:
++++DATABASES['default']+=+{'ENGINE':+'sqlite3'}|1002174|最后在Django+1.3和1.4中：|1002175|if+'test'+in+sys.argv:
++++DATABASES['default']+=+{'ENGINE':+'django.db.backends.sqlite3'}|1002176|(对于Django+1.3，到后端的完整路径并不是必须的，但可以使设置向前兼容。)|1002177|您还可以添加以下行，以防您在南迁移时遇到问题：|1002178|++++SOUTH_TESTS_MIGRATE+=+False|1002179|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.djangoproject.com/en/dev/ref/settings/#s-std:setting-TEST_NAME^0|S|10|0|0|8|B|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@$A|19|B|1A|1|1B]]|C|$]]|$1|D|3|E|5|6|7|1C|8|@$A|1D|B|1E|F|G]]|9|@]|C|$]]|$1|H|3|I|5|J|7|1F|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|1G|8|@]|9|@]|C|$]]|$1|O|3|P|5|J|7|1H|8|@]|9|@]|C|$K|L]]|$1|Q|3|R|5|6|7|1I|8|@]|9|@]|C|$]]|$1|S|3|T|5|J|7|1J|8|@]|9|@]|C|$K|L]]|$1|U|3|V|5|6|7|1K|8|@]|9|@]|C|$]]|$1|W|3|X|5|6|7|1L|8|@]|9|@]|C|$]]|$1|Y|3|Z|5|J|7|1M|8|@]|9|@]|C|$K|L]]|$1|10|3|-4|5|6|7|1N|8|@]|9|@]|C|$]]]|11|$12|$5|13|14|15|C|$16|17]]]]

If you set your database engine to sqlite3 when you run your tests, <a href="https://docs.djangoproject.com/en/dev/ref/settings/#s-std:setting-TEST_NAME" rel="noreferrer">Django will use a in-memory database</a>.

I'm using code like this in my <code>settings.py</code> to set the engine to sqlite when running my tests:

<pre><code>if 'test' in sys.argv:
 DATABASE_ENGINE = 'sqlite3'
</code></pre>

Or in Django 1.2:

<pre><code>if 'test' in sys.argv:
 DATABASES['default'] = {'ENGINE': 'sqlite3'}
</code></pre>

And finally in Django 1.3 and 1.4:

<pre><code>if 'test' in sys.argv:
 DATABASES['default'] = {'ENGINE': 'django.db.backends.sqlite3'}
</code></pre>

(The full path to the backend isn't strictly necessary with Django 1.3, but makes the setting forward compatible.)

You can also add the following line, in case you are having problems with South migrations:

<pre><code> SOUTH_TESTS_MIGRATE = False
</code></pre>

blocks|key|1216573|text|在Anurag的回答的基础上扩展，我通过创建相同的test_settings并向manage.py添加以下内容简化了该过程|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1216574|if+len(sys.argv)+>+1+and+sys.argv[1]+==+"test":
++++os.environ.setdefault("DJANGO_SETTINGS_MODULE",+"mysite.test_settings")
else:
++++os.environ.setdefault("DJANGO_SETTINGS_MODULE",+"mysite.settings")|code-block|syntax|javascript|1216575|看起来更整洁，因为sys已经导入，而manage.py只能通过命令行使用，所以不需要弄乱设置|1216576|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Extending on Anurag's answer I simplified the process by creating the same test_settings and adding the following to manage.py

<pre><code>if len(sys.argv) &gt; 1 and sys.argv[1] == "test":
 os.environ.setdefault("DJANGO_SETTINGS_MODULE", "mysite.test_settings")
else:
 os.environ.setdefault("DJANGO_SETTINGS_MODULE", "mysite.settings")
</code></pre>

seems cleaner since sys is already imported and manage.py is only used via command line, so no need to clutter up settings

blocks|key|1002261|text|在您的setting.py中使用以下内容|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1002262|DATABASES['default']['ENGINE']+=+'django.db.backends.sqlite3'|code-block|syntax|javascript|1002263|entityMap^0|3|A|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

Use below in your <code>setting.py</code>

<pre><code>DATABASES['default']['ENGINE'] = 'django.db.backends.sqlite3'
</code></pre>

My Django unit tests take a long time to run, so I'm looking for ways to speed that up. I'm considering installing an <a href="http://en.wikipedia.org/wiki/Solid-state_drive" rel="noreferrer">SSD</a>, but I know that has its downsides too. Of course, there are things I could do with my code, but I'm looking for a structural fix. Even running a single test is slow since the database needs to be rebuilt / south migrated every time. So here's my idea...

Since I know the test database will always be quite small, why can't I just configure the system to always keep the entire test database in RAM? Never touch the disk at all. How do I configure this in Django? I'd prefer to keep using <a href="http://en.wikipedia.org/wiki/MySQL" rel="noreferrer">MySQL</a> since that's what I use in production, but if <a href="http://en.wikipedia.org/wiki/SQLite" rel="noreferrer">SQLite</a>&nbsp;3 or something else makes this easy, I'd go that way.

Does SQLite or MySQL have an option to run entirely in memory? It should be possible to configure a RAM disk and then configure the test database to store its data there, but I'm not sure how to tell Django / MySQL to use a different data directory for a certain database, especially since it keeps getting erased and recreated each run. (I'm on a Mac FWIW.)

How to run Django's test database only in memory?

我的Django单元测试需要很长时间才能运行，所以我正在寻找加速的方法。我正在考虑安装一个，但我知道这也有它的缺点。当然，我可以用我的代码做一些事情，但我正在寻找一个结构修复。即使运行一次测试也很慢，因为每次都需要重新构建/南迁移数据库。我的想法是..。既然我知道测试数据库总是很小，为什么我不能简单地将系统配置为始终将...

问如何只在内存中运行Django的测试数据库？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何只在内存中运行Django的测试数据库？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何只在内存中运行Django的测试数据库？
EN