Real time ranking django scalability issue
I am making a real time sports ranking application using django and Postgressql and my performance time seems to be alright as of one user. However, I use save signals to update related models entirely without any cache. I was wondering how I could maintain the real time ranking and updating aspect but take the load off of my server and database. I have looked into django-channels, PUSHER, and redis but am unsure of where to go. Any help is appreciated.
python django caching scaling
asked Nov 14 '18 at 23:28
Ty CTy C
399
add a comment |
I am making a real time sports ranking application using django and Postgressql and my performance time seems to be alright as of one user. However, I use save signals to update related models entirely without any cache. I was wondering how I could maintain the real time ranking and updating aspect but take the load off of my server and database. I have looked into django-channels, PUSHER, and redis but am unsure of where to go. Any help is appreciated.
python django caching scaling
asked Nov 14 '18 at 23:28
Ty CTy C
399
i dont understand what your question is... none of those alternatives would necessarily "take the load off your server" ... what do you even mean when you say "take the load off my server"? why do you think that you will run into scaling issues using your current method?
– Joran Beasley
Nov 14 '18 at 23:46
I am afraid concurrent requests and utilization of my database will cause it to delay significantly?
– Ty C
Nov 14 '18 at 23:59
2
and is this just some gut feeling? or you have some measurments to back this up? also what does "delay significantly" mean? 1 second is a ton of time to a PC ... but its pretty inconsequential to a human. a pretty smart guy once said "Premature optimization is the root of all evil"
– Joran Beasley
Nov 15 '18 at 0:01
I second @JoranBeasley. My experience of Django and Postgressql databases are that they are fast and robust. If you haven't actually experienced any delay in production then I wouldn't be concerned.
– Asher
Nov 15 '18 at 0:43
add a comment |
I am making a real time sports ranking application using django and Postgressql and my performance time seems to be alright as of one user. However, I use save signals to update related models entirely without any cache. I was wondering how I could maintain the real time ranking and updating aspect but take the load off of my server and database. I have looked into django-channels, PUSHER, and redis but am unsure of where to go. Any help is appreciated.
python django caching scaling
asked Nov 14 '18 at 23:28
Ty CTy C
399
I am making a real time sports ranking application using django and Postgressql and my performance time seems to be alright as of one user. However, I use save signals to update related models entirely without any cache. I was wondering how I could maintain the real time ranking and updating aspect but take the load off of my server and database. I have looked into django-channels, PUSHER, and redis but am unsure of where to go. Any help is appreciated.
python django caching scaling
python django caching scaling
asked Nov 14 '18 at 23:28
Ty CTy C
399
asked Nov 14 '18 at 23:28
Ty CTy C
399
asked Nov 14 '18 at 23:28
Ty CTy C
399
asked Nov 14 '18 at 23:28
Ty CTy C
399
asked Nov 14 '18 at 23:28
Ty CTy C
399
399
i dont understand what your question is... none of those alternatives would necessarily "take the load off your server" ... what do you even mean when you say "take the load off my server"? why do you think that you will run into scaling issues using your current method?
– Joran Beasley
Nov 14 '18 at 23:46
I am afraid concurrent requests and utilization of my database will cause it to delay significantly?
– Ty C
Nov 14 '18 at 23:59
2
and is this just some gut feeling? or you have some measurments to back this up? also what does "delay significantly" mean? 1 second is a ton of time to a PC ... but its pretty inconsequential to a human. a pretty smart guy once said "Premature optimization is the root of all evil"
– Joran Beasley
Nov 15 '18 at 0:01
I second @JoranBeasley. My experience of Django and Postgressql databases are that they are fast and robust. If you haven't actually experienced any delay in production then I wouldn't be concerned.
– Asher
Nov 15 '18 at 0:43
add a comment |
i dont understand what your question is... none of those alternatives would necessarily "take the load off your server" ... what do you even mean when you say "take the load off my server"? why do you think that you will run into scaling issues using your current method?
– Joran Beasley
Nov 14 '18 at 23:46
I am afraid concurrent requests and utilization of my database will cause it to delay significantly?
– Ty C
Nov 14 '18 at 23:59
2
and is this just some gut feeling? or you have some measurments to back this up? also what does "delay significantly" mean? 1 second is a ton of time to a PC ... but its pretty inconsequential to a human. a pretty smart guy once said "Premature optimization is the root of all evil"
– Joran Beasley
Nov 15 '18 at 0:01
I second @JoranBeasley. My experience of Django and Postgressql databases are that they are fast and robust. If you haven't actually experienced any delay in production then I wouldn't be concerned.
– Asher
Nov 15 '18 at 0:43
i dont understand what your question is... none of those alternatives would necessarily "take the load off your server" ... what do you even mean when you say "take the load off my server"? why do you think that you will run into scaling issues using your current method?
– Joran Beasley
Nov 14 '18 at 23:46
i dont understand what your question is... none of those alternatives would necessarily "take the load off your server" ... what do you even mean when you say "take the load off my server"? why do you think that you will run into scaling issues using your current method?
– Joran Beasley
Nov 14 '18 at 23:46
I am afraid concurrent requests and utilization of my database will cause it to delay significantly?
– Ty C
Nov 14 '18 at 23:59
I am afraid concurrent requests and utilization of my database will cause it to delay significantly?
– Ty C
Nov 14 '18 at 23:59
2
2
and is this just some gut feeling? or you have some measurments to back this up? also what does "delay significantly" mean? 1 second is a ton of time to a PC ... but its pretty inconsequential to a human. a pretty smart guy once said "Premature optimization is the root of all evil"
– Joran Beasley
Nov 15 '18 at 0:01
and is this just some gut feeling? or you have some measurments to back this up? also what does "delay significantly" mean? 1 second is a ton of time to a PC ... but its pretty inconsequential to a human. a pretty smart guy once said "Premature optimization is the root of all evil"
– Joran Beasley
Nov 15 '18 at 0:01
I second @JoranBeasley. My experience of Django and Postgressql databases are that they are fast and robust. If you haven't actually experienced any delay in production then I wouldn't be concerned.
– Asher
Nov 15 '18 at 0:43
I second @JoranBeasley. My experience of Django and Postgressql databases are that they are fast and robust. If you haven't actually experienced any delay in production then I wouldn't be concerned.
– Asher
Nov 15 '18 at 0:43
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53310308%2freal-time-ranking-django-scalability-issue%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53310308%2freal-time-ranking-django-scalability-issue%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
i dont understand what your question is... none of those alternatives would necessarily "take the load off your server" ... what do you even mean when you say "take the load off my server"? why do you think that you will run into scaling issues using your current method?
– Joran Beasley
Nov 14 '18 at 23:46
I am afraid concurrent requests and utilization of my database will cause it to delay significantly?
– Ty C
Nov 14 '18 at 23:59
2
and is this just some gut feeling? or you have some measurments to back this up? also what does "delay significantly" mean? 1 second is a ton of time to a PC ... but its pretty inconsequential to a human. a pretty smart guy once said "Premature optimization is the root of all evil"
– Joran Beasley
Nov 15 '18 at 0:01
I second @JoranBeasley. My experience of Django and Postgressql databases are that they are fast and robust. If you haven't actually experienced any delay in production then I wouldn't be concerned.
– Asher
Nov 15 '18 at 0:43