从节点请求Couchbase的并行DB请求。jsSDK-parallelDBrequeststoCouchbasefromNode.jsSDK

3  

Don't make separate connections, that I don't suggest. It only adds extra load on the database. You can add connections for other databases, but not the for the same database.

不要建立单独的联系，我不建议这样做。它只会增加数据库的额外负载。您可以为其他数据库添加连接，但不能为相同的数据库添加连接。

You have a couple of choices:

你有几个选择:

1. Make multiple requests anytime you get to know a number of keys. As you said this might not scale well. I suggest you try this and test it to see how it goes, since it's easiest to implement. If it matches the requirements then use this. Luckily in Node.js requests are actually asynchronous, so they are done in parallel actually, and the docs focus is non-asynchronous programming languages, so it might not be that bad. But the database will have to do to extra work. With this solution, you might have shortest latency to obtain a single key value.

   无论何时，只要知道了几个键，就可以发出多个请求。就像你说的，这可能不太好。我建议您尝试一下并测试它，看看它是如何运行的，因为它是最容易实现的。如果它匹配需求，那么使用这个。幸运的是在节点。js请求实际上是异步的，所以它们实际上是并行执行的，而文档关注的是非异步编程语言，所以可能没有那么糟糕。但是数据库需要做额外的工作。使用这个解决方案，您可能有最短的延迟来获得一个键值。

2. If the timespan that all the keys come is short as half milisecond(it's really a short time!), just wait for them to all come and make a bulk request. Make sure your half milisecond will not become 200 millisecond on heavy load! If it's always that short, then this will be a better solution.

   如果所有键的时间间隔都短到半毫秒(真的是很短的时间!)，那就等它们都来了，然后大量请求。确保你的半毫秒在负重时不会变成200毫秒!如果它总是那么短，那么这将是一个更好的解决方案。

3. Make a queue and use a hybrid approach. If the above suggestions don't work well on all situations, you may try this: Whenever you need a key, push to the queue. Check the queue on a time interval and get the keys in the queue together and clear the queue. The time interval can be something like 5ms or 10ms or even more. Depending on how fast the keys come and how fast you need them. You have test this solution with heavy load on different settings to tune it well. With this you might get low latency for getting the result of a single key value, and also not putting extra load on database.

   创建一个队列并使用混合方法。如果上面的建议在所有情况下都不能很好地工作，您可以尝试这样做:当您需要密钥时，按下队列。检查队列的时间间隔，将队列中的键放在一起，清除队列。时间间隔可以是5ms或10ms甚至更多。取决于键的速度和你需要它们的速度。您已经对这个解决方案进行了测试，并在不同的设置上使用了大量的负载，以便对其进行优化。使用这种方法，您可能会获得一个键值的结果的低延迟，并且不会给数据库增加额外的负载。