Spring-MVC与原始Servlet:内存消耗，性能 [英] Spring-MVC vs. raw Servlet: memory consumption, performance

问题描述

我正在阅读问题原始Servlet与Spring MVC" ，想知道Spring MVC与原始servlet相比是否会减慢或炸毁应用程序的内存消耗?

I was reading the question "Raw Servlet vs. Spring MVC" and was wondering if Spring MVC might slow down or blow up the memory consumption of your application compared with raw servlet?

注意:我最初是在上面提到的问题中要求它作为评论，然后被传唤为一个单独的问题.

Note: I originally asked it as a comment in the question mentioned above and was then kindly summoned to post it as a separate question.

推荐答案

定义爆炸".定义减速".

Define "blow up". Define "slow down".

当然，内存使用率会更高，而性能会更低.

Of course memory usage will be higher, and of course performance will be lower.

与Spring提供的其他功能和灵活性相比，有多少更高和更低?这是 real 问题，对假设的应用程序一无所知，这是不可能的

How much higher, and lower compared to the additional functionality and flexibility Spring provides is the real question, and not knowing anything about the hypothetical app, it's impossible to say.

构建一个可测试的，可扩展的，结构良好的仅servlet的应用程序将涉及重新实现Spring提供的许多功能.您想做什么?将一些(基本上)行业标准的代码重新实现到已实现的程度，然后编写您的应用程序，或者只是编写您的应用程序?您的老板会喜欢哪个呢?

Building a testable, extensible, well-architected servlet-only app would involved re-implementing a lot of the functionality Spring provides. Which would you prefer to do--re-implement some (essentially) industry-standard code to the same degree it's been implemented and then write your app, or just write your app? And which would your boss prefer you do?

这篇关于Spring-MVC与原始Servlet:内存消耗，性能的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！