Allright,
Deploying with verbosity=0 solved my problem.
Something is happening in that self.log( call at line 112 that make it
crash on Heroku. Unsure what it is and unsure the issue is on Django side.
At least this resolves my problem and there is some reference if someone
else encounter th
Hi,
The "remote: Found another file with the destination path" is not actually
an error, I actually have thousands of those and it is normal. It's simply
suppose to be a warning that was added in version 1.9:
https://github.com/django/django/commit/5304494585c58b0c9245ea9896a6d6122a8673a2
"Added
> Den 3. feb. 2016 kl. 22.30 skrev Joshua Pokotilow :
>
> At the startup where I work, we've written a lot of our server code in
> Django. So far, we've adopted a "build it fast" mentality, so we invested
> very little time in optimizing our code. A small amount of load testing has
> revealed
Thanks Simon this works great so far =^)
-bobby
> On Feb 3, 2016, at 12:34 PM, Simon Charette wrote:
>
> Hi Bobby,
>
> I'm not sure this is what you are looking for but it looks like
> `connection_created`[1] signal might do.
>
> Cheers,
> Simon
>
> [1] https://docs.djangoproject.com/en/1.9
On Wed, Feb 3, 2016 at 11:30 PM, Joshua Pokotilow
wrote:
> At the startup where I work, we've written a lot of our server code in
> Django. So far, we've adopted a "build it fast" mentality, so we invested
> very little time in optimizing our code. A small amount of load testing has
> revealed ou
As you said the project is using DRF for an API, it came to my mind some
blog post I've read about it:
-
http://ses4j.github.io/2015/11/23/optimizing-slow-django-rest-framework-performance/
-
https://www.dabapps.com/blog/api-performance-profiling-django-rest-framework/
-
htt
While optimizing the code will bring you improvements and you shouldn't
stop doing this, for the most part (as noted from Rafael's resources)
you should update your architecture to support Django in scaling.
As you mentioned, instead of hitting the DB for every multi-second API
call you scale it
Joshua,
My team is producing a Django app with a small number of
users, so we haven't worried too much about performance yet,
but we know we may have to some day, so I've accumulated a
list of ways to improve performance in a JIRA ticket for if/when
it becomes
Hi Bobby,
I'm not sure this is what you are looking for but it looks like
`connection_created`[1] signal might do.
Cheers,
Simon
[1] https://docs.djangoproject.com/en/1.9/ref/signals/#connection-created
Le mercredi 3 février 2016 12:25:36 UTC-5, Bobby Mozumder a écrit :
>
> I'm looking to use
I'm looking to use PREPARE/EXECUTE statements, to eliminate my Query Planning
time from every Web request.
This can be done via SQL PREPARE/EXECUTE statements.
But, Postgres only supports PREPARE statements on a connection
session-by-session basis.
To do this with Django, I need to be able t
Thank you! I agree that we need to investigate before coming up with a
solution.
On Wednesday, February 3, 2016 at 11:11:04 AM UTC-5, Avraham Serour wrote:
>
> if your problem is the DB or network or small processor it won't help
> rewriting the application.
> The first step is to investigate th
Thanks Remco. I'll look at High Performance Django.
On Wednesday, February 3, 2016 at 11:05:11 AM UTC-5, Remco Gerlich wrote:
>
> There is a book (ebook) named "High Performance Django" that has many
> useful tips.
>
> Also, new software developers are _always_ skeptical when they start a new
>
Thank you Sergiy! I agree that the code needs to be fixed.
We don't have a Tomcat endpoint to compare with, although I did scare my
coworkers a bit when we profiled a Django endpoint that took 300 - 400ms to
return a response due (ostensibly) in large part to form object
instantiation. Specific
Thanks Bill. This was helpful. I understand that it's difficult to offer
advice without too many specifics, so I'm hoping to get some high-level
advice / examples of Django at scale, which you provided.
Thank you!
On Wednesday, February 3, 2016 at 10:49:51 AM UTC-5, Bill Blanchard wrote:
>
> Le
I don't think there is a silver bullet that will fix all issues, nor
any one technology stack that will. I have a fairly good size django
app I built, and I did not consider performance all that much during
initial development. As the user base and dataset started to grow I
did see performance issu
if your problem is the DB or network or small processor it won't help
rewriting the application.
The first step is to investigate the problem, then you can have solution,
sometimes people have a solution and then look for a problem, in your case
they want to leave python and django and are looking
Sorry for the double-post, but I just searched the Django Developers group,
and found this: "Using EXISTS instead of IN for subqueries"
https://groups.google.com/forum/#!searchin/django-developers/WHERE$20EXISTS/django-developers/OG1unUV-MOU/VzkepyuaUDUJ
and this: "Support server-side cursors for
There is a book (ebook) named "High Performance Django" that has many
useful tips.
Also, new software developers are _always_ skeptical when they start a new
job. They have an old way of doing things from their previous job, "that's
not how we work here!" reflexes also from that old job, and they
Greetings!
I'm trying to refactor a query to avoid using QuerySet.extra (as per the
recommendation here:
https://docs.djangoproject.com/en/1.9/ref/models/querysets/#extra)
Here's a simplified version of my code:
# testapp.models
class Parent(models.Model):
pass
class Child(models.Model):
The service uses the Django REST Framework and takes multiple seconds to
return a response. The response is a JSON array with thousands of
dictionaries. We haven't yet investigated why it's slow, nor have we tried
to cache / memoize anything to speed it up.
On Wednesday, February 3, 2016 at 10:
Hello,
Your first words have a answer. Swift coding always produces performance
problem. This is expected. Looks like few new engineers use another one
technology and would not like to use django. This a reason of his
criticism. Mostly low performance is related to the DB performance. I'm
Let's try to adress some of their concerns:
- We need to move to a service-oriented infrastructure because Django is
> too monolithic
It depends on what your application does and what you're planning to do
with it in the future. People are quick prescribe SOA as the end all way
to scale, but th
Maybe I don't understand you very well, and for shure you have a very
specific problem to solve... but... do you read something of this?
http://blog.disqus.com/post/62187806135/scaling-django-to-8-billion-page-views
https://www.digitalocean.com/community/tutorials/how-to-scale-django-beyond-the-ba
what do you mean by slow? can you measure in ms?
On Wed, Feb 3, 2016 at 5:30 PM, Joshua Pokotilow
wrote:
> At the startup where I work, we've written a lot of our server code in
> Django. So far, we've adopted a "build it fast" mentality, so we invested
> very little time in optimizing our code.
At the startup where I work, we've written a lot of our server code in
Django. So far, we've adopted a "build it fast" mentality, so we invested
very little time in optimizing our code. A small amount of load testing has
revealed our codebase / infrastructure as it stands today needs to run
fas
http://chimera.labs.oreilly.com/books/123400754/index.html
On 3 February 2016 at 14:33, Rafael E. Ferrero wrote:
> For Python
> https://www.codecademy.com/learn/python
> https://www.hackerrank.com/domains/python/py-introduction
>
> For Django
> https://docs.djangoproject.com/en/1.9/
>
>
>
> R
Hello Denis,
This issue is not related to the django-require. Look like you have
two files (with same name ) at the different paths. New collect static
is trying to colelct both files and can not decided which one should be
used.
Could you please send part of the section STATICFILES_DI
For Python
https://www.codecademy.com/learn/python
https://www.hackerrank.com/domains/python/py-introduction
For Django
https://docs.djangoproject.com/en/1.9/
Rafael E. Ferrero
2016-02-03 8:30 GMT-03:00 Ajay Sharma :
> Hi everyone on the Group.
>
> I want resources and web links, where i can
If you don't have access to the shell, why are you concerned with the
django version?
On 3 February 2016 at 13:05, wrote:
> Hello,
>
> and if not ?
>
> i have actually only acces to the web part.
>
> Le mardi 2 février 2016 18:43:56 UTC+1, James Bennett a écrit :
>>
>> As long as you have access
Hi Django Experts.
I have recently migrated my Django app to Django 1.8.8 since then I am
experiencing low performance.
With cProfiling I am have generated following breakdown of time spent.
ncalls tottime percall cumtime percall filename:lineno(function)
49 22.0430.450
Hi,
I'm looking at upgrading my application from 1.6 to 1.9.2... An issue I'm
encountering now is that on Heroku, running collectstatic doesn't work on
1.9.2. The odd things is that if I try 1.8.7 instead, it work great...
Running:
remote: python manage.py collectstatic -i docs -i tests --noinp
I've been stuck on this issue for a while now. If anyone have concrete
solution please let me know.
I subscribed for a VPS on DigitalOcean.com Ubuntu with OneClickDjango
installation. Pre-loaded installation is 1.6.1 and when I upgrade it I get
Programming Error django_content_type already exist
Hi everyone on the Group.
I want resources and web links, where i can learn Django Framework On
Linux platform as I
am using Ubuntu for the development.
Please help me .
thank you to every one in Advance.
>From Ajay . :)
--
You received this message because you are subscribed to the
django --version
--
林攀
在 2016-02-03 19:05:01，communicat...@domainedemanville.fr 写道：
Hello,
and if not ?
i have actually only acces to the web part.
Le mardi 2 février 2016 18:43:56 UTC+1, James Bennett a écrit :
As long as you have access to a shell, you can do
python manage.py she
Hello,
and if not ?
i have actually only acces to the web part.
Le mardi 2 février 2016 18:43:56 UTC+1, James Bennett a écrit :
>
> As long as you have access to a shell, you can do
>
> python manage.py shell
>
> Then in the interpreter, do
>
> import django
> print(django.get_version())
>
> O
35 matches
Mail list logo
