Ibm mobilefirst Worklight适配器性能

如果我处于这种情况，我想从Worklight server的角度了解适配器调用是如何工作的：

基本上，我们正在为几个（n）适配器定义一个体系结构，这些适配器必须使用一个公共函数。 我们计划创建一个专用适配器来实现这一点，因此，通过这种方式，每个适配器都应该能够使用WL.Server.invokeProcedure API调用这个“公共”过程

疑问在于，如果来自调用此“公共”适配器的多个n适配器的大量请求（y）可能会在Worklight Server上出现性能问题，因为该服务器在单个过程中接收大量调用

我的理解是（或者至少得到官方确认）：如果Worklight server在适配器（尤其是HTTP适配器）的单个过程上接收到大量调用，那么如何管理这些调用（例如，WL Server使用不同线程为每次调用并行管理不同的调用，或者将它们放入队列？）以及是否在不同适配器之间使用另一个适配器共享过程是一种常见做法（以及我们是否可以使用另一种方法避免对WL Server进行额外调用）

---

我已经阅读了性能和可伸缩性文档，但没有注意到关于这一点的信息。

关于适配器的性能设置，您可能感兴趣的一个方面是 maxConcurrentConnectionsPerNode

maxConcurrentConnectionsPerNode – The maximum number of concurrent requests that can be 
performed on the back-end application from the Worklight server node. This 
maxConcurrentConnectionsPerNode parameter is set in the adapter.xml in the connectivity 
entry.


There are two considerations when setting this parameter:

    If there is no limitation in the back-end about the incoming connections then, 
a "Rough" rule of thumb will be to set the number of connection threads per adapter 
to be the number of  http threads in the application server. A more precise rule 
of thumb will be to understand the percent of requests going to each back-end and 
set the number respectively.

    The back-end may have a limitation on the incoming connection threads: In that case 
we can have only BACKEND_MAX_CONNECTIONS/NUM_OF_CLUSTER_NODES connection threads where 
BACKEND_MAX_CONNECTIONS is the maximum incoming connections define in the back-end 
server and  NUM_OF_CLUSTER_NODES is the number Worklight server nodes in the cluster.

您还可以查看Tuning Worklight Server文档，该文档涵盖了上面提到的一些方面：

---

关于适配器的性能设置，您可能感兴趣的一个方面是 maxConcurrentConnectionsPerNode

maxConcurrentConnectionsPerNode – The maximum number of concurrent requests that can be 
performed on the back-end application from the Worklight server node. This 
maxConcurrentConnectionsPerNode parameter is set in the adapter.xml in the connectivity 
entry.


There are two considerations when setting this parameter:

    If there is no limitation in the back-end about the incoming connections then, 
a "Rough" rule of thumb will be to set the number of connection threads per adapter 
to be the number of  http threads in the application server. A more precise rule 
of thumb will be to understand the percent of requests going to each back-end and 
set the number respectively.

    The back-end may have a limitation on the incoming connection threads: In that case 
we can have only BACKEND_MAX_CONNECTIONS/NUM_OF_CLUSTER_NODES connection threads where 
BACKEND_MAX_CONNECTIONS is the maximum incoming connections define in the back-end 
server and  NUM_OF_CLUSTER_NODES is the number Worklight server nodes in the cluster.

您还可以查看Tuning Worklight Server文档，该文档涵盖了上面提到的一些方面：

---

关于适配器的性能设置，您可能感兴趣的一个方面是 maxConcurrentConnectionsPerNode

maxConcurrentConnectionsPerNode – The maximum number of concurrent requests that can be 
performed on the back-end application from the Worklight server node. This 
maxConcurrentConnectionsPerNode parameter is set in the adapter.xml in the connectivity 
entry.


There are two considerations when setting this parameter:

    If there is no limitation in the back-end about the incoming connections then, 
a "Rough" rule of thumb will be to set the number of connection threads per adapter 
to be the number of  http threads in the application server. A more precise rule 
of thumb will be to understand the percent of requests going to each back-end and 
set the number respectively.

    The back-end may have a limitation on the incoming connection threads: In that case 
we can have only BACKEND_MAX_CONNECTIONS/NUM_OF_CLUSTER_NODES connection threads where 
BACKEND_MAX_CONNECTIONS is the maximum incoming connections define in the back-end 
server and  NUM_OF_CLUSTER_NODES is the number Worklight server nodes in the cluster.

您还可以查看Tuning Worklight Server文档，该文档涵盖了上面提到的一些方面：

---

关于适配器的性能设置，您可能感兴趣的一个方面是 maxConcurrentConnectionsPerNode

maxConcurrentConnectionsPerNode – The maximum number of concurrent requests that can be 
performed on the back-end application from the Worklight server node. This 
maxConcurrentConnectionsPerNode parameter is set in the adapter.xml in the connectivity 
entry.


There are two considerations when setting this parameter:

    If there is no limitation in the back-end about the incoming connections then, 
a "Rough" rule of thumb will be to set the number of connection threads per adapter 
to be the number of  http threads in the application server. A more precise rule 
of thumb will be to understand the percent of requests going to each back-end and 
set the number respectively.

    The back-end may have a limitation on the incoming connection threads: In that case 
we can have only BACKEND_MAX_CONNECTIONS/NUM_OF_CLUSTER_NODES connection threads where 
BACKEND_MAX_CONNECTIONS is the maximum incoming connections define in the back-end 
server and  NUM_OF_CLUSTER_NODES is the number Worklight server nodes in the cluster.

您还可以查看Tuning Worklight Server文档，该文档涵盖了上面提到的一些方面：