Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Discussion" <users@myfaces.apache.org>
Received-SPF: pass (athena.apache.org: domain of smithh032772@gmail.com
 designates 209.85.212.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAPyf0gdak6EAfq5b5pEXdtEcb6Spx+pqtbqx5nDwAJ1MhCcwMw@mail.gmail.com>
References: 
 <CAGV1rDKCQsyQitoGVdVu2gmeTKwGFY3nW+n-436Coi=zXg2WRw@mail.gmail.com>
	<CAPCnv12nv_acr5jNHe1BJKy3_PGQpsaU2btu3_NamFYbb0YxmA@mail.gmail.com>
	<CAAuOd=UvV71RUMrQ49=cTVN3cL1xyih-Fbz6QPuAVAdpj79i5w@mail.gmail.com>
	<CAGV1rDKsX5OQiBkfMYWufkzez78psqKinkoAxOdqmhx4H1rkuw@mail.gmail.com>
	<1382271473.16319.YahooMailNeo@web28905.mail.ir2.yahoo.com>
	<CAGV1rDKsUvw=E9ftPT2_+gFWRh7QH+6HHSN=j7Vx0i22kjXW7g@mail.gmail.com>
	<CAGV1rDLPwn7gD5q_fCxiooE8yExgnH-f1Ex3Z=Qe2GfCuOnmuw@mail.gmail.com>
	<CAPyf0gem+7sW-Pm55MLFC40BTQr7LgVfNiySR2rJ0L=LhLZh+Q@mail.gmail.com>
	<CAGV1rDL_pGF_9ouP1XH692J5UhGyNaCZuoySQ17agreQKPt4Rw@mail.gmail.com>
	<CAPyf0gdWGKE29_HW2N=mM-X8GOnV57D0jOgqAokK-RXvQdnY1g@mail.gmail.com>
	<CAGV1rDKFtfvK0Yip=aFeRPrT-n8oRX29AH2D_mgyQ_fPgz8X3g@mail.gmail.com>
	<CAPyf0gdak6EAfq5b5pEXdtEcb6Spx+pqtbqx5nDwAJ1MhCcwMw@mail.gmail.com>
Date: Sun, 20 Oct 2013 23:40:20 -0400
Message-ID: 
 <CAGV1rD+jSq9+yGQU8UyQN1naMGMKqAiN3rKXP1bLWn834eR7iA@mail.gmail.com>
Subject: Re: [OT but still JSF]: Clustering, session replication, and
 database, too
From: "Howard W. Smith, Jr." <smithh032772@gmail.com>
To: MyFaces Discussion <users@myfaces.apache.org>
Content-Type: multipart/alternative; boundary=047d7b5d439614521404e9380bed

--047d7b5d439614521404e9380bed
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

how many concurrent users is your app serving....normally or at peak times?

earlier, i think you mentioned response time is quite fast. did you throw
fast/high-performance hardware at db server, so db server responds fasts to
queries/updates?

do you have any expensive queries or updates...that may cause other
endusers to wait for a few seconds (or more)...if multiple users are using
your app, concurrently?

any (other db) performance issues that you'd like to share or you know
can/should be optimized to improve response time since one database is
serving 2 tomee/jsf/ear layer?


On Sun, Oct 20, 2013 at 9:03 PM, Jos=E9 Luis Cetina <maxtorzito@gmail.com>w=
rote:

> El 20/10/2013 19:34, "Howard W. Smith, Jr." <smithh032772@gmail.com>
> escribi=F3:
> >
> > so, db server is on a separate machine/server on the network, and each
> EAR
> > is referencing the (one) db server via IP address?
> >
>
> Yes 2 tomee instances each in separete server point to a third server tha=
t
> only serve as db server. Thats why y have clustering only in webapps and
> not in db.
>
> > also, do you have an embedded db server (running inside of tomee and
> using
> > tomcat jdbc pooling) or network db server/engine?
> >
> >
>
> I use tomcat jdbc pooling (tomee with defined connections in tomee.xml)
>
> > On Sun, Oct 20, 2013 at 5:32 PM, Jos=E9 Luis Cetina <maxtorzito@gmail.c=
om
> >wrote:
> >
> > > Ear with all my apps in each server (2 server each with their own ear=
)
> then
> > > each server insert/read in another unique db server.
> > > El 20/10/2013 16:09, "Howard W. Smith, Jr." <smithh032772@gmail.com>
> > > escribi=F3:
> > >
> > > > Hmmm, i thought you said that you have EAR on one server and databa=
se
> on
> > > > separate server. are you running 2 tomee on same server; one tomee =
=3D
> EAR,
> > > > another tomee =3D database?
> > > >
> > > >
> > > >
> > > > On Sun, Oct 20, 2013 at 11:52 AM, Jos=E9 Luis Cetina <
> maxtorzito@gmail.com
> > > > >wrote:
> > > >
> > > > > By the way im not using remote calls. All my apps are in the same
> ear
> > > > with
> > > > > this i can inject my ejb local interface for calling methods in
> ejb.
> > > > > El 20/10/2013 07:49, "Howard W. Smith, Jr." <
> smithh032772@gmail.com>
> > > > > escribi=F3:
> > > > >
> > > > > > just remembered-and-revised 2nd question, below...
> > > > > >
> > > > > > On Sun, Oct 20, 2013 at 8:35 AM, Howard W. Smith, Jr. <
> > > > > > smithh032772@gmail.com> wrote:
> > > > > >
> > > > > > >
> > > > > > > On Sun, Oct 20, 2013 at 8:17 AM, Mark Struberg <
> struberg@yahoo.de>
> > > > > > wrote:
> > > > > > >
> > > > > > >> This can also be very helpful to 'scale out' in case you nee=
d
> > > > > > performance:
> > > > > > >>
> > > > > > >> All write stuff is only performed on the master node, but
> > > expensive
> > > > > > >> queries/searches might be performed on the n replication
> nodes. Of
> > > > > > course
> > > > > > >> this needs a special handling in your app, but allows to mov=
e
> the
> > > > > > expensive
> > > > > > >> queries away from your primary node.
> > > > > > >>
> > > > > > >
> > > > > > > hmmm, had a question or two, or seeking clarification (or a b=
it
> > > more
> > > > > > > details or even a reference to a blog/article/document).
> > > > > > >
> > > > > > > 1. scale-out usually mean different physical servers? scaling
> out
> > > > > > multiple
> > > > > > > databases on one physical server, usually (or I would assume)
> means
> > > > > that
> > > > > > > the hard drive becomes the bottleneck, if hard drive contain
> > > multiple
> > > > > > > databases. right?
> > > > > > >
> > > > > > > 2. this needs special handling in your app? can you please
> clarify?
> > > > > > >
> > > > > > >
> > > > > > thanks!
> > > > > >
> > > > >
> > > >
> > >
>

--047d7b5d439614521404e9380bed--