作者:我爱超人宝宝 | 来源:互联网 | 2023-05-18 12:13
IjustfinishedwhatIwouldcallasmalldjangoprojectandprettysoonitsgoinglive.Itsonly
I just finished what I would call a small django project and pretty soon it's going live. It's only 6 models but a fairly complex view layer and a lot of records saving and retrieving.
我刚刚完成了我称之为小型django的项目,很快它就会上线。它只有6个模型,但是相当复杂的视图层和大量记录保存和检索。
Of course, forgetting the obvious huge amount of bugs that will, probably, fill my inbox to the top, what would it be the next step towards a website with best performance. What could be tweaked?
当然,忘记明显的大量错误,可能会将我的收件箱填入顶部,这对于具有最佳性能的网站而言是下一步。什么可以调整?
I'm using jmeter a lot recently and feel confident that I have a good baseline for future performance comparisons, but the thing is: I'm not sure what is the best start, since I'm a greedy bastard that wants to work the least possible and gather the best results.
我最近经常使用jmeter并且对我未来的性能比较有一个很好的基线,但事实是:我不确定什么是最好的开始,因为我是一个贪婪的混蛋想要工作最不可能并收集最好的结果。
For instance, should I try an approach towards infrastructure, like a distributed database, or should I go with the code itself and in that case, is there something that specifically results in better performance? In your experience, whats pays off more?
例如,我应该尝试一种基础设施的方法,比如分布式数据库,还是我应该使用代码本身,在这种情况下,是否有某些特定的结果会带来更好的性能?根据您的经验,最新的回报是什么?
As a personal contribution: I sometimes have the impression that some operations, when done through django's signals, are faster then the usual view way. But hey, I'm biased. I freaking loooove signals. :)
作为个人贡献:我有时会觉得有些操作,通过django的信号完成,比通常的查看方式更快。但是,嘿,我有偏见。我疯狂的信号。 :)
Personal anecdotes like mine, are welcome as a way to stimulate some research, but some fact based opinions are much more appreciated. :)
像我这样的个人轶事是一种刺激一些研究的方式,但是一些基于事实的观点更受欢迎。 :)
Thanks very much.
非常感谢。
2 个解决方案