This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
Hey all, in our Maximo 7.1 environment we have a dedicated report server (a BROS, as it has been called). Just wondering what the consensus would be on a safe value to set mxe.report.birt.maxconcurrentrun considering we have a dedicated server. We have a need to set it higher than 5.
Kevin Wertz
Grifols Therapeutics, Inc
Hi,
That depends on the set up of your BROS bro. (Sorry I could not resist that.:-))
We have a server with four processors and 2GB for each processor with a cluster of four application servers. Our maxconcurrentrun is 40. Works just fine.
Dave Bone
--- In MAXIMO@yahoogroups.com, "kevwertz" <wertzee@...> wrote:
>
> Hey all, in our Maximo 7.1 environment we have a dedicated report server (a BROS, as it has been called). Just wondering what the consensus would be on a safe value to set mxe.report.birt.maxconcurrentrun considering we have a dedicated server. We have a need to set it higher than 5.
>
> Kevin Wertz
> Grifols Therapeutics, Inc
>
We have plenty of processing power so not too worried about that. I guess the next question would be if you have ever even observed a large amount of reports hitting at one time. We will have reports being emailed at 2am as soon as the wogen runs so we are certain it will generate at least 15-20 per minute.
KW
Sent from my iPhone
On May 4, 2012, at 1:34 PM, "in2data" <in2data@yahoo.com> wrote:
> Hi,
>
> That depends on the set up of your BROS bro. (Sorry I could not resist that.:-))
>
> We have a server with four processors and 2GB for each processor with a cluster of four application servers. Our maxconcurrentrun is 40. Works just fine.
>
> Dave Bone
>
> --- In MAXIMO@yahoogroups.com, "kevwertz" <wertzee@...> wrote:
> >
> > Hey all, in our Maximo 7.1 environment we have a dedicated report server (a BROS, as it has been called). Just wondering what the consensus would be on a safe value to set mxe.report.birt.maxconcurrentrun considering we have a dedicated server. We have a need to set it higher than 5.
> >
> > Kevin Wertz
> > Grifols Therapeutics, Inc
> >
>
>
Hi,
We have a lot of users that can schedule reports to run. One has 26 reports scheduled to run all at 0515 each morning. He reports no problems at all. Other users are using the system at the same time and report no issues.
Dave Bone
--- In MAXIMO@yahoogroups.com, Kevin Wertz <wertzee@...> wrote:
>
> We have plenty of processing power so not too worried about that. I guess the next question would be if you have ever even observed a large amount of reports hitting at one time. We will have reports being emailed at 2am as soon as the wogen runs so we are certain it will generate at least 15-20 per minute.
>
> KW
>
> Sent from my iPhone
>
> On May 4, 2012, at 1:34 PM, "in2data" <in2data@...> wrote:
>
> > Hi,
> >
> > That depends on the set up of your BROS bro. (Sorry I could not resist that.:-))
> >
> > We have a server with four processors and 2GB for each processor with a cluster of four application servers. Our maxconcurrentrun is 40. Works just fine.
> >
> > Dave Bone
> >
> > --- In MAXIMO@yahoogroups.com, "kevwertz" <wertzee@> wrote:
> > >
> > > Hey all, in our Maximo 7.1 environment we have a dedicated report server (a BROS, as it has been called). Just wondering what the consensus would be on a safe value to set mxe.report.birt.maxconcurrentrun considering we have a dedicated server. We have a need to set it higher than 5.
> > >
> > > Kevin Wertz
> > > Grifols Therapeutics, Inc
> > >
> >
> >
>
>
>
>
Thanks Dave...after looking closer, it turned out we had a server instance
property set already to change the concurrentrun to 20 for our BROS.
Strange thing is though that it was still only doing 5 at a time. It wasn't
until we set the global maxconcurrentrun setting that the BROS actually
started running more than 5 at a time. We ran a test in a dev environment
generating 20 reports in conjunction with a wogen and the BROS barely broke
a sweat.
KW
On Mon, May 7, 2012 at 12:16 PM, in2data <in2data@yahoo.com> wrote:
> **
>
>
> Hi,
>
> We have a lot of users that can schedule reports to run. One has 26
> reports scheduled to run all at 0515 each morning. He reports no problems
> at all. Other users are using the system at the same time and report no
> issues.
>
> Dave Bone
>
>
> --- In MAXIMO@yahoogroups.com, Kevin Wertz <wertzee@...> wrote:
> >
> > We have plenty of processing power so not too worried about that. I
> guess the next question would be if you have ever even observed a large
> amount of reports hitting at one time. We will have reports being emailed
> at 2am as soon as the wogen runs so we are certain it will generate at
> least 15-20 per minute.
> >
> > KW
> >
> > Sent from my iPhone
> >
> > On May 4, 2012, at 1:34 PM, "in2data" <in2data@...> wrote:
> >
> > > Hi,
> > >
> > > That depends on the set up of your BROS bro. (Sorry I could not resist
> that.:-))
> > >
> > > We have a server with four processors and 2GB for each processor with
> a cluster of four application servers. Our maxconcurrentrun is 40. Works
> just fine.
> > >
> > > Dave Bone
> > >
> > > --- In MAXIMO@yahoogroups.com, "kevwertz" <wertzee@> wrote:
> > > >
> > > > Hey all, in our Maximo 7.1 environment we have a dedicated report
> server (a BROS, as it has been called). Just wondering what the consensus
> would be on a safe value to set mxe.report.birt.maxconcurrentrun
> considering we have a dedicated server. We have a need to set it higher
> than 5.
> > > >
> > > > Kevin Wertz
> > > > Grifols Therapeutics, Inc
> > > >
> > >
> > >
> >
> >
> >
> >
>
>
>