如何配置 Firebird 数据库在内存中运行

发布于 2024-08-19 18:05:14 字数 192 浏览 4 评论 0原文

我正在运行一个名为 Fishbowl inventory 的软件,它在 firebird 数据库(Windows server 2003)上运行,此时当超过一个用户访问该软件时,fishbowl 软件运行速度非常慢。我想我也许可以通过强制数据库在“内存中”运行来加速应用程序。但是我找不到有关如何执行此操作的文档。任何帮助将不胜感激。

先感谢您。 罗伯特

I'm running a software called Fishbowl inventory and it is running on a firebird database (Windows server 2003) at this time the fishbowl software is running extremely slow when more then one user accesses the software. I'm thinking I maybe able to speed up the application by forcing the database to run "In Memory". However I can not find documentation on how to do this. Any help would be greatly appreciated.

Thank you in advance.
Robert

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(4

思慕 2024-08-26 18:05:14

Firebird 没有内存表 - 它们可能会也可能不会在未来版本 (>3) 中添加,但肯定不会在即将到来的 2.5 中添加。可能还有许多其他原因导致您的软件在多个用户的情况下运行缓慢;然而,Firebird 本身具有相当好的并发性,因此请确保首先找到实际的瓶颈。

Firebird does not have memory tables - they may or may not be added in future versions (>3) but certainly not in the upcoming 2.5. There can be any other number of reasons why your software is slow with multiple users; however, Firebird itself has pretty good concurrency, so make sure you find the actual bottleneck first.

漆黑的白昼 2024-08-26 18:05:14

霍尔格+1。首先找到瓶颈。
Sinática Monitor可能会帮助您。

+1 to Holger. Find the bottleneck first.
Sinática Monitor may help you.

原野 2024-08-26 18:05:14

内存表对于 OLAP(当数据不更改时)或临时内部数据存储都很有用。
在这两种情况下,数据丢失都不会有危险。

遗憾的是FB没有内存模式。我考虑使用 SQLite 作为结果。

至于缓存,我认为读取数据库文件所有块的简单并行线程将使其位于内存中 - 如果操作系统有足够的内存,则位于操作系统缓存中。

但我也认为,操作系统已经缓存了尽可能多的数据库文件,并且积极强制缓存会使整体性能变得更糟。

In-memory tables are nice either for OLAP (when data is not changing) or for temporary internal data storage.
In both cases data loss is not danger.

Pity that FB has no in-memory mode. I think about using SQLite as result.

As for caching, i think simple parallel thread that reads all the blocks of database file would make it in-memory - in OS cache if OS has enough memory.

But i also think, that OS already cached as much of DB file as it could and agressive forcing to cache would make overall performance even worse.

暖树树初阳… 2024-08-26 18:05:14

我不久前读过一篇文章,作者是一位制作内存驱动器(如旧 DOS 中的驱动器)并在那里运行数据库的人。问题是,如果任何事情失败,你就会失去一切。您应该经常进行备份以确保最低限度的安全性。

我认为根本不是一个好主意。

I had read an article some time ago, from someone who did a memory drive (like in old DOS) and ran a Database there. The problem is if anything fails, you lose everything. You should do backups very often to ensure a minimum of security.

Not a good idea at all I think.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文