You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@syncope.apache.org by Lukas Funk <Lu...@united-security-providers.ch> on 2018/11/29 07:16:22 UTC
Performance Blog
Hi all,
I've just read the blog post about the performance benchmarking - http://blog.tirasa.net/benchmarking-apache-syncope-on-postgresql.html - and I'm thrilled!
This was a concern which bothered myself quite a bit and but with the results presented, I thinks there is a solution in near reach to overcome this issue.
Thanks for your all efforts whoever was involved making this happen and to Francesco for the blog post! I'm looking forward to it!
One thing which I can't judge but I'd be interested in: What's impact on existing installations? Is there a "easy" migration path for such?
Maybe someone can elaborate with a few lines about it before the release update guide is out.
We're running on a 2.0.X version and are planning to update to 2.1.X and of course would like to profit from the new performance gain as soon as it's released.
Regards, Lukas
Re: Performance Blog
Posted by Francesco Chicchiriccò <il...@apache.org>.
On 29/11/18 08:16, Lukas Funk wrote:
>
> Hi all,
>
> I’ve just read the blog post about the performance benchmarking -
> http://blog.tirasa.net/benchmarking-apache-syncope-on-postgresql.html
> - and I’m thrilled!
>
> This was a concern which bothered myself quite a bit and but with the
> results presented, I thinks there is a solution in near reach to
> overcome this issue.
>
> Thanks for your all efforts whoever was involved making this happen
> and to Francesco for the blog post! I’m looking forward to it!
>
Thanks Lukas, I knew you would have appreciated :-)
> One thing which I can’t judge but I’d be interested in: What’s impact
> on existing installations? Is there a “easy” migration path for such?
>
> Maybe someone can elaborate with a few lines about it before the
> release update guide is out.
>
While changing an existing deployment from 2.1.3 "PostgreSQL
traditional" to 2.1.3 "PostgreSQL JSONB" is indeed possible, the process
is not trivial: there should be something able to read the existing
users / groups / any objects (with their attributes and values) in the
previous format, e.g. from the ?PlainAttr, ?PlainAttrValue and
?PlainAttrUniqueValue tables, create their JSON representation according
to the new format, and write them down into the appropriate fields of
the SyncopeUser / SyncopeGroup / AnyObject tables.
Alternatively, especially if the existing deployment is not based on
PostgreSQL, one could take an approach similar to the one proposed for
1.2 -> 2.0 migration [1], e.g. prepare a second, empty 2.1.3 PostgreSQL
JSONB deployment and pull from the existing deployment as an external
Scripted REST resource.
As said, not trivial either ways...
> We’re running on a 2.0.X version and are planning to update to 2.1.X
> and of course would like to profit from the new performance gain as
> soon as it’s released.
>
[1]
https://syncope.apache.org/docs/2.0/reference-guide.html#migration-from-apache-syncope-1-2
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
http://home.apache.org/~ilgrosso/