如何优化远程 d/b 访问？
我怀疑问题出在“远程”上，并认为问题更有可能出在“d/b 访问”上 - 但是，我怎么知道？
我可以/应该优化我的实际 d/b 结构吗？也许添加外键等
或使用循环d/b来限制记录数？或者定期将某些行“离线”移动？
也许我可以优化我的 SQL（使用内/外连接等）？
Fwiw，标准是 d/b write，有人抱怨它“太慢”；很少有人阅读（只是其中一种情况，您存储数据“以防万一需要”）
有什么建议、网站、书籍吗？是否有任何 ValGrind 类型的工具来测量/分析实际发生的情况？
I doubt that the problem is with "remote", and think it more likely to be with "d/b access" - but, how can I know?
Can/should I optimze my actual d/b structure? maybe adding foreign keys, etc
Or use a round robin d/b to limit the number of records? Or move some rows "offline" on a regular basis?
Maybe I can optimize my SQL (use of inner/outer join, etc)?
Fwiw, the norm is d/b write, which is complained of as being "too slow"; there are very few reads (just one of those cases where you store data "just in case it is needed")
Any advice, web-sites, books? Are there any ValGrind-type tools to measure/profile what is actually happening?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
离开我的头顶。 。 。
它实际上需要什么，以及什么
您的应用程序在此期间做什么
时间？如果不这样做，请使用秒表
还有什么办法。
当您在本地访问数据库时是否执行相同的任务？
HTTP、VPN、VNC、ssh？
结构和行数。
数据库？通过直接表访问，或者
存储过程？
优化。 外键是
数据完整性的基础。在你被解雇之前添加它们。
on Rails、Django、ASP？他们提供哪些设施来记录他们的表现？
Off the top of my head . . .
does it actually take, and what
does your application do during that
time? Use a stopwatch if you don't
have any other way.
does the same task take when you access the database locally?
HTTP, VPN, VNC, ssh?
structure and number of rows.
the database? Through direct table access, or
stored procedures?
optimization. Foreign keys are
fundamental to data integrity. Add them before you get fired.
on rails, Django, ASP? What facilities do they offer to log their performance?