RavenDB 或 SQL Server 2008 文件流
我目前正在进行的一个项目涉及将大量结果存储在文件中，并根据这些结果进行计算。我一直在考虑使用 RavenDB 或使用带有 Filestream 的 SQL2008 作为结果的存储。我不确定哪种技术最适合我的问题。
有人对这些方法中哪种最适合大规模存储和可能的结果搜索有什么看法吗？
A project I am working on at the minute involves taking a massive set of results stored in a file and doing calculations based on those results. I have been looking at using either RavenDB or using the SQL2008 with the Filestream as the storage for the results. I am not sure which technology would be best suited to my problem.
Has anyone any views on which of these approaches is best for massive storage and possible searching of results?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我尝试向 Raven 插入大量数据，但一开始也很失望，因为我是通过一个线程完成这一切的。事实证明，插入到 SQL Server 的速度更快（无需在两台服务器上进行太多配置）。
然后我意识到我可能误用了 Raven，据我所知，Raven 是为处理大规模并行而设计的。所以我玩了一下 TPL，打开了很多线程/进程来并行插入。 Raven 处理得很好 - 但请记住“最终一致性” - 并非所有结果都会立即显示在数据库中，而是会出现短暂的延迟。
我认为直接比较是很困难的，除非您调整架构以适应所选的存储技术。
I tried to insert a lot of data to Raven and was also disappointed in the first place, because I did it all form one thread. It turned out that inserting to SQL Server was faster (without doing much configuration on both servers).
Then I realized that I probably misused Raven, which is - as far as I understand it - designed to handle massive parallelism. So I played a bit with TPL opening a lot of threads / processes doing inserts in parallel. Raven handled this very well - but keep the "eventual consistency" in mind - not all the results showed up in the database immediatly but with a short delay.
I think a direct comparrison is hard unless you adjust your architecture to fit the choosen storage technology.