War for each portlet could affect performance or not

[Ghulam Shabbir, modificado 9 Anos atrás.]

Hi ,

I have about 10 to 12 war for each portlet, can this have bad affect on performance ?

Regards,
Abbas

[Suresh Nimmakayala, modificado 9 Anos atrás.]

first i didn't get it 10 to 12 war for each portlet ?

i am guessing based on the subject you have 10-12 wars for every portlet(10 -12 portlets)

how is your server performance,never tried i have 50-60 portlets but all in one project(.war)

for deployment, setting dev enronment, development i reckon in single war/project is good ,

may be you thought/requirement if i am changing a single portlet/service why we need re build/deploy all ? because i thought that way sometimes

hope someone tried this already comparing ( portlets in single war vs multiple wars)and got results

[David H Nebinger, modificado 9 Anos atrás.]

Ghulam Shabbir:

Hi ,

I have about 10 to 12 war for each portlet, can this have bad affect on performance ?

Regards,
Abbas

Yes. As separate wars, the app server startup time will be delayed while each separate war is loaded and started.

Possibly (unless you've done things right) you may have duplicate resources in separate apps (i.e. separate wars having separate connections to the same database).

If you serve anything directly from the servlet side of the war, then you are incurring memory overhead for session storage (I think you get a session object whether you store anything in it or not). With session replication in a cluster, this may add extra overhead to keep sessions in sync across the cluster.

Now, all of that said, I wouldn't advocate pushing them all into a single war. Usually I recommend grouping related portlets (related by function, dependency on external resource, etc), but that's only when there is a clear relation.