Hi everyone!
My name is Chetan Khanna. I'm one of the applicants for GSOC this summer. I had
written a proposal for the GraphQL topic and posted it to the forum a week
back. But with all the virus situation everywhere, couldn't really get it
reviewed property. So I had a request for the communi
Hi,
I'd like to point out that the MySQL backend uses the mysqld utility to
create a database dump which is then imported. So, as far as implementation
complexity goes, I believe migration once again during setup of the child
process might complicate it further. It might just be easier to use on-d
You’re both most likely correct, but I think it’s good to get some numbers and
compare implementation complexity.
It’s also worth considering that often as a project grows in complexity the
time it takes to do a full test run grows with it, so perhaps the overhead
would be in a fairly constant
I agree with Adam here, it not just about running the SQL itself; the
current migration framework require models to be (re-)rerendered before a
lot of schema operations which slows down dramatically as project grows.
The dump/restore approach will undeniably be faster than running migrations
fo
>
> I just finished rewriting it to re-run migrations and setup in each
> worker. I didn't bench mark it so I'll do that again later, but as a gut
> reaction it isn't significantly slower; but of course the numbers will tell
> the real story.
I'm a little concerned about rerunning migrations in e
Hi All.
Calendar Week 12 -- ending 22 March.
Triaged:
https://code.djangoproject.com/ticket/30311 -- Can't replace global
admin actions with specialized ones per-admin (Accepted)
https://code.djangoproject.com/ticket/31380 -- Deploy system check that
DJANGO_ALLOW_ASYNC_UNSAFE is not set (
You're definitely right!
I just finished rewriting it to re-run migrations and setup in each worker.
I didn't bench mark it so I'll do that again later, but as a gut reaction
it isn't significantly slower; but of course the numbers will tell the real
story.
Passing the dump string through shared
Hi Nikita. Thanks for the follow up. C.
On Mon, 30 Mar 2020 at 13:56, Никита Соболев wrote:
> Hi everyone,
>
> I am one of the django-stubs core-devs (https://github.com/sobolevn).
>
> I would love to mentor Kacper and help with anything django-stubs related.
> You can count me in!
>
> Best rega
Hi everyone,
I am one of the django-stubs core-devs (https://github.com/sobolevn).
I would love to mentor Kacper and help with anything django-stubs related.
You can count me in!
Best regards,
Nikita Sobolev
суббота, 28 марта 2020 г., 2:08:07 UTC+3 пользователь Kacper Szmigiel
написал:
>
> Hel
Hi everyone,
I am one of the TypedDjango maintainers (https://github.com/sobolevn)
I know there are people who want to work on this project during GSoC.
I want to confirm that I am able and willing to mentor several people.
Cheers!
среда, 25 марта 2020 г., 11:43:49 UTC+3 пользователь Carlton Gi
Week ending March 29, 2020.
*Triaged:*
https://code.djangoproject.com/ticket/31395 - Make TestCase.setUpTestData
enforce in-memory data isolation. (accepted)
https://code.djangoproject.com/ticket/31394 - Impossible to create with an
inverse one-to-one relationship. (invalid)
https://code.djangop
Awesome! However there is always a tradeoff between speed and code complexity -
it might not be worth a more complex system involving shared memory or copying
SQLite files in other ways if it only saves ~5 seconds at the start of a test
run compared to re-running the migrations in each worker. I
I did stumble upon shared memory when I originally wanted to pass the
database connection itself into shared memory. Your idea of passing the
query string is MUCH more reasonable, can be done using shared memory, and
will ultimately be much more cleanly written.
i'll definitely test out if it has
There is an interesting addition to the standard library in Python 3.8:
multiprocessing.shared_memory
(https://docs.python.org/3/library/multiprocessing.shared_memory.html). It’s
only on 3.8 but it might be worth seeing if that has a performance improvement
over passing a large string into the
Thank you Adam for the amazing pointer. That's exactly the solution I was
looking for.
I didn't even know VACUUM INTO was a thing in SQLite3 (quite nifty). Both
sources you listed can definitely copy memory-to-memory efficiently. I had
also found two useful APIs in the standard library's documenta
15 matches
Mail list logo
