<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Tim,<br>
<br>
The situation that you are experiencing is most likely caused by
current implementation of midPoint GUI and provisioning. The
current implementation is still using sequential read (GUI) and
update (provisioning) of resources. This sequential approach
provided many benefits in the past, mostly for troubleshooting
during midPoint stabilization periods. But these times are over
now. We have been planning to switch to parallel processing for
some time already. The architecture is ready for this and the
implementation should be relatively easy. <br>
<br>
The root cause are especially those two issues:<br>
<a class="moz-txt-link-freetext" href="https://jira.evolveum.com/browse/MID-770">https://jira.evolveum.com/browse/MID-770</a><br>
<a class="moz-txt-link-freetext" href="https://jira.evolveum.com/browse/MID-2350">https://jira.evolveum.com/browse/MID-2350</a><br>
<br>
While this is obviously needed to make midPoint work well in an
environment with thousands of resources, midPoint subscribers
haven't chosen to "vote" for any of these issues yet. Therefore we
are moving them out from release to release and preferring the
issues that midPoint subscribers marked as more important. My
opinion is that parallel provisioning in midPoint is very
important. But as midPoint development is funded from
subscriptions and sponsoring we need to listen closely to what
subscribers and sponsors say and prioritize development according
to that.<br>
<br>
Therefore you have the usual options:<br>
<a class="moz-txt-link-freetext" href="https://wiki.evolveum.com/display/midPoint/I+Need+New+Feature">https://wiki.evolveum.com/display/midPoint/I+Need+New+Feature</a><br>
<br>
My estimate is that if there is some way how to fund the
development both improvements could still fit into the midPoint
3.3 release.<br>
<br>
<pre class="moz-signature" cols="72">--
Radovan Semancik
Software Architect
evolveum.com
</pre>
<br>
<br>
On 08/17/2015 05:03 PM, <a class="moz-txt-link-abbreviated" href="mailto:Tim.Strong@sita.aero">Tim.Strong@sita.aero</a> wrote:<br>
</div>
<blockquote
cite="mid:OFDCFA56C4.122163B6-ON85257EA4.004F4BDD-85257EA4.0052BB8C@sita.aero"
type="cite"><font size="2" face="sans-serif">Hi folks,</font>
<br>
<font size="2" face="sans-serif">Can anyone provide insight and/or
real
life experience on how midPoint behaves & scales for
literally hundreds
of AD sites.</font>
<br>
<br>
<font size="2" face="sans-serif">We have hundreds of small AD
sites scattered
in all sorts of places, and as I am running through my PoC to
bring some
test reources onto midPoint, I've noticed a performance hit on
midPoint
when it talks to a "slower site" to retrieve shadow account
information.
It could be slower because of bandwidth or slower because of
the
server hardware.</font>
<br>
<br>
<font size="2" face="sans-serif">While I was pulling the
architecture
together, I got into my head that reaching out to
resources/shadow accounts
would be minimal since it is stored in the repository. I gather
this
is not the case (unless the wiki is not up to date on caching,
virtual
approach & meta approach).</font>
<br>
<br>
<font size="2" face="sans-serif">Am I correct in my thinking that
my
performance will continue to degrade the more resource accounts
I link
to a user? (By performance, I mean anytime a user is clicked in
UI
to list their info & resource accounts.) Is there anyway to
overcome
this?</font>
<br>
<br>
<font size="2" face="sans-serif">Tim</font>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
midPoint mailing list
<a class="moz-txt-link-abbreviated" href="mailto:midPoint@lists.evolveum.com">midPoint@lists.evolveum.com</a>
<a class="moz-txt-link-freetext" href="http://lists.evolveum.com/mailman/listinfo/midpoint">http://lists.evolveum.com/mailman/listinfo/midpoint</a>
</pre>
</blockquote>
<br>
</body>
</html>