哪个负载均衡器在性能mod_jk或mod_proxy或任何其他开源方面会更好

时间:2021-09-28 16:52:58

I am willing to host an application in a single machine with out any fail-over or load balancing at the hardware level as per my budget.

我愿意在一台机器上托管一个应用程序,而不是根据我的预算在硬件级别进行任何故障转移或负载平衡。

But, to my knowledge, as the no of hits increases to the tomcat, it has a drawback of going down. So, to get rid of that I want to go with multiple instances for the same application. So to do so, which load balancer would be better either mod_jk or mod_proxy. You can even suggest any other open source tool that helps me in load balancing the application hits.

但是,据我所知,随着tomcat的命中率增加,它有一个下降的缺点。因此,为了摆脱这种情况,我想为同一个应用程序使用多个实例。所以要做到这一点,哪个负载均衡器会更好mod_jk或mod_proxy。您甚至可以建议任何其他开源工具,帮助我平衡应用程序命中。

My application contains structs and not even springs and my OS is rhel 6.x. Please suggest according to the good performance also.

我的应用程序包含结构,甚至不包括弹簧,我的操作系统是rhel 6.x.请根据良好的表现建议。

Thanks in advance.

提前致谢。

1 个解决方案

#1


Running multiple instances of one application on the same machine only leads to the application sharing the resources - minus the overhead for the additional Tomcat instances and the loadbalancer.

在同一台计算机上运行一个应用程序的多个实例只会导致应用程序共享资源 - 减去额外Tomcat实例和负载均衡器的开销。

This is pretty much the same as dividing cargo on individual tires because a car gets slow when it is too loaded. Staying in the picture: what you want is a turbocharger.

这与在单个轮胎上分割货物几乎相同,因为当货车太载时汽车会变慢。保持图片:你想要的是涡轮增压器。

Translated that would be a reverse proxy cache.

翻译,这将是一个反向代理缓存。

I'd suggest using varnish. You can configure it to serve static resources like images and stylesheets from RAM after they were delivered the first time, reducing the requests passed to your application drastically.

我建议使用清漆。您可以将其配置为在第一次交付时从RAM中提供静态资源(如图像和样式表),从而大大减少传递给应用程序的请求。

It may be configured as a classical load balancer, too.

它也可以配置为经典的负载均衡器。

#1


Running multiple instances of one application on the same machine only leads to the application sharing the resources - minus the overhead for the additional Tomcat instances and the loadbalancer.

在同一台计算机上运行一个应用程序的多个实例只会导致应用程序共享资源 - 减去额外Tomcat实例和负载均衡器的开销。

This is pretty much the same as dividing cargo on individual tires because a car gets slow when it is too loaded. Staying in the picture: what you want is a turbocharger.

这与在单个轮胎上分割货物几乎相同,因为当货车太载时汽车会变慢。保持图片:你想要的是涡轮增压器。

Translated that would be a reverse proxy cache.

翻译,这将是一个反向代理缓存。

I'd suggest using varnish. You can configure it to serve static resources like images and stylesheets from RAM after they were delivered the first time, reducing the requests passed to your application drastically.

我建议使用清漆。您可以将其配置为在第一次交付时从RAM中提供静态资源(如图像和样式表),从而大大减少传递给应用程序的请求。

It may be configured as a classical load balancer, too.

它也可以配置为经典的负载均衡器。