简体   繁体   English

GemStone-Linux-Apache-Seaside-Smalltalk .. 4GB的实用性如何?

[英]GemStone-Linux-Apache-Seaside-Smalltalk.. how practical is 4GB?

I am really interested in GLASS . 我对GLASS很感兴趣。 The 4GB limit for the free version has me concerned. 免费版的4GB限制令我担忧。 Especially when I consider the price for the next level ($7000 year). 特别是当我考虑下一个级别的价格 (7000美元)。

  1. I know this can be subjective and variable, but can someone describe for me in everyday terms what 4 GB of GLASS will get you? 我知道这可能是主观的和可变的,但有人可以在日常用语中为我描述4 GB的GLASS会给你带来什么? Maybe a business example. 也许是一个商业榜样。 4 GB may get me more storage than I realize.. and I don't have to worry about it. 4 GB可能比我意识到的更多存储空间...而且我不必担心它。

  2. In my app, some messages have file attachments up to 5 MB in size. 在我的应用程序中,某些邮件的文件附件大小最大为5 MB。 Can I conserve the 4 GB of Gemstone space by saving these attachments directly to files on the operating system, instead of inside Gemstone? 我可以通过将这些附件直接保存到操作系统上的文件而不是Gemstone中来保存4 GB的Gemstone空间吗? I'm thinking yes. 我在想是的。

I'm aware of one GLASS system that is ~944 MB and has 8.3 million objects, or ~118 bytes per object. 我知道一个GLASS系统大约944 MB,有830万个对象,或者每个对象大约118个字节。 At this rate, it can grow to over 36 million objects and stay under 4 GB. 按照这个速度,它可以增长到超过3600万个对象并保持在4 GB以下。

As to "attachments", I'd suggest that even in an RDBMS you should consider storing larger, static data in the file system and referencing it from the database. 至于“附件”,我建议即使在RDBMS中,您也应该考虑在文件系统中存储较大的静态数据并从数据库中引用它。 If you are building a web-based application, serving static content (JPG, CSS, etc.) should be done by your web server (eg, Apache) rather than through the primary application. 如果要构建基于Web的应用程序,则应通过Web服务器(例如Apache)而不是主应用程序来提供静态内容(JPG,CSS等)。

By comparison, Oracle and Microsoft SQL Server have no-cost licenses for a 4-GB database. 相比之下,Oracle和Microsoft SQL Server拥有4 GB数据库的免费许可证。

What do you think would be a good price for the next level? 您认为下一个级别的价格会是多少?

The 4GByte limit has been removed a while ago. 4GByte限制已被删除。 The free version is limited now to the use of two cores and 2GByte ram. 免费版现在仅限于使用两个内核和2GByte内存。

4GB is quite a decent size database. 4GB是一个相当不错的大小数据库。 Not having used gemstone before I can only speculate as to how efficient it is a storing objects, but having played with a few other similar object databases (Mongodb, db4o). 我之前没有使用过宝石,我只能推测它是多么有效的存储对象,但是玩了一些其他类似的对象数据库(Mongodb,db4o)。 I know that you're going to be able to fit several(5-10) million records before you even get close to that limit. 我知道在你接近这个限制之前,你将能够容纳几(5-10)万条记录。 In reality, how many records depends highly on the type of data you're storing. 实际上,有多少记录在很大程度上取决于您要存储的数据类型。

As an example I was storing ~2million listings & ~1million transactions, in a mysql database and the space was < 1Gb. 作为一个例子,我在一个mysql数据库中存储了大约200万个列表和~1百万个事务,空间<1Gb。 You have a small overhead serializing a whole object, but not that much. 序列化整个对象的开销很小,但不是那么多。

Files can definitely can be stored on the file system. 文件绝对可以存储在文件系统中。

4gb一个问题......我猜你认为你正在构建下一个ebay!

Nowadays, there is no limit on the size of the repository. 如今,存储库的大小没有限制。 See the latest specs for GemStone 查看GemStone的最新规格

如果您有多个同时具有5MB附件的用户,则无论如何都需要单独的策略,因为每个用户占用GBit以太网网络的第二十分之一带宽。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM