[JBoss JIRA] Created: (ISPN-1267) IsMarshallableInterceptor causes unnecessary marshalling in remote access mode
3:25 p.m.
IsMarshallableInterceptor causes unnecessary marshalling in remote access mode
------------------------------------------------------------------------------
Key: ISPN-1267
URL: https://issues.jboss.org/browse/ISPN-1267
Project: Infinispan
Issue Type: Bug
Components: Marshalling
Affects Versions: 5.0.0.CR8
Reporter: Michal Linhard
Assignee: Manik Surtani
this is because by default GenericJBossMarshaller is used and
GenericJBossMarshaller.isMarshallable implementation marshalls objects to find whether
they are marshallable.
this proves to be a very significant performance bottleneck, see details in JBPAPP-6865
in remote access storeAsBinary shouldn't have any performance impact, because the
values that are received on serverside are already byte arrays.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:02 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-1267) IsMarshallableInterceptor causes unnecessary marshalling in remote access mode
[
https://issues.jboss.org/browse/ISPN-1267?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-1267:
----------------------------------------
Slightly intrigued about the expensiveness of GJM.isMarshallable() cos even though it
could be improved (it could skip all basic types, including byte[]), once it's tried
to marshall a byte[], the type and the result of isMarshallable is cached in a
ConcurrentWeakKeyHashMap. So, the rest should be straight map lookups.
It's true too that storeAsBinary does not make sense with any servers could data is
already stored as byte[] or String in the case of Memcached keys. That can be forced on
HRS startup.
I'm checking the last jprofiler snapshots available to try to understand this better.
Thanks Michal!
IsMarshallableInterceptor causes unnecessary marshalling in remote
access mode
------------------------------------------------------------------------------
Key: ISPN-1267
URL: https://issues.jboss.org/browse/ISPN-1267
Project: Infinispan
Issue Type: Bug
Components: Marshalling
Affects Versions: 5.0.0.CR8
Reporter: Michal Linhard
Assignee: Manik Surtani
Fix For: 5.0.0.FINAL
this is because by default GenericJBossMarshaller is used and
GenericJBossMarshaller.isMarshallable implementation marshalls objects to find whether
they are marshallable.
this proves to be a very significant performance bottleneck, see details in JBPAPP-6865
in remote access storeAsBinary shouldn't have any performance impact, because the
values that are received on serverside are already byte arrays.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:02 a.m.
New subject: [JBoss JIRA] Assigned: (ISPN-1267) IsMarshallableInterceptor causes unnecessary marshalling in remote access mode
[
https://issues.jboss.org/browse/ISPN-1267?page=com.atlassian.jira.plugin....
]
Galder Zamarreño reassigned ISPN-1267:
--------------------------------------
Assignee: Galder Zamarreño (was: Manik Surtani)
IsMarshallableInterceptor causes unnecessary marshalling in remote
access mode
------------------------------------------------------------------------------
Key: ISPN-1267
URL: https://issues.jboss.org/browse/ISPN-1267
Project: Infinispan
Issue Type: Bug
Components: Marshalling
Affects Versions: 5.0.0.CR8
Reporter: Michal Linhard
Assignee: Galder Zamarreño
Fix For: 5.0.0.FINAL
this is because by default GenericJBossMarshaller is used and
GenericJBossMarshaller.isMarshallable implementation marshalls objects to find whether
they are marshallable.
this proves to be a very significant performance bottleneck, see details in JBPAPP-6865
in remote access storeAsBinary shouldn't have any performance impact, because the
values that are received on serverside are already byte arrays.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:02 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-1267) IsMarshallableInterceptor causes unnecessary marshalling in remote access mode
[
https://issues.jboss.org/browse/ISPN-1267?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-1267:
-----------------------------------
Fix Version/s: 5.0.0.FINAL
IsMarshallableInterceptor causes unnecessary marshalling in remote
access mode
------------------------------------------------------------------------------
Key: ISPN-1267
URL: https://issues.jboss.org/browse/ISPN-1267
Project: Infinispan
Issue Type: Bug
Components: Marshalling
Affects Versions: 5.0.0.CR8
Reporter: Michal Linhard
Assignee: Galder Zamarreño
Fix For: 5.0.0.FINAL
this is because by default GenericJBossMarshaller is used and
GenericJBossMarshaller.isMarshallable implementation marshalls objects to find whether
they are marshallable.
this proves to be a very significant performance bottleneck, see details in JBPAPP-6865
in remote access storeAsBinary shouldn't have any performance impact, because the
values that are received on serverside are already byte arrays.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:39 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-1267) IsMarshallableInterceptor causes unnecessary marshalling in remote access mode
[
https://issues.jboss.org/browse/ISPN-1267?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-1267:
----------------------------------------
More than the isMarshallable implementation, I think it's the fact that
MarshalledValue instances are created left and right and these are compacted. MVs are
created cos we store wrappers (ByteArrayKey and CacheValue) but the whole storeAsBinary
does not make sense in the first place anyway.
So, the solution here is for server startup to disable storeAsBinary/lazyDeserialization.
That should apply to HR, Memcached and REST servers too.
IsMarshallableInterceptor causes unnecessary marshalling in remote
access mode
------------------------------------------------------------------------------
Key: ISPN-1267
URL: https://issues.jboss.org/browse/ISPN-1267
Project: Infinispan
Issue Type: Bug
Components: Marshalling
Affects Versions: 5.0.0.CR8
Reporter: Michal Linhard
Assignee: Galder Zamarreño
Fix For: 5.0.0.FINAL
this is because by default GenericJBossMarshaller is used and
GenericJBossMarshaller.isMarshallable implementation marshalls objects to find whether
they are marshallable.
this proves to be a very significant performance bottleneck, see details in JBPAPP-6865
in remote access storeAsBinary shouldn't have any performance impact, because the
values that are received on serverside are already byte arrays.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:45 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-1267) IsMarshallableInterceptor causes unnecessary marshalling in remote access mode
[
https://issues.jboss.org/browse/ISPN-1267?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-1267:
----------------------------------------
Btw, JProfiler snapshots such as the ones in
https://issues.jboss.org/browse/JBPAPP-6865?focusedCommentId=12616268&...
look buggy. For a hotrod server put, MVI should be creating two MarshalledValue instances
but the profiler shows no calls to MVI.createMarshalledValue(). I've verified this
with Michal where he's tried to do a put on a HR endpoint in EDG and he can confirm
this.
IsMarshallableInterceptor causes unnecessary marshalling in remote
access mode
------------------------------------------------------------------------------
Key: ISPN-1267
URL: https://issues.jboss.org/browse/ISPN-1267
Project: Infinispan
Issue Type: Bug
Components: Marshalling
Affects Versions: 5.0.0.CR8
Reporter: Michal Linhard
Assignee: Galder Zamarreño
Fix For: 5.0.0.FINAL
this is because by default GenericJBossMarshaller is used and
GenericJBossMarshaller.isMarshallable implementation marshalls objects to find whether
they are marshallable.
this proves to be a very significant performance bottleneck, see details in JBPAPP-6865
in remote access storeAsBinary shouldn't have any performance impact, because the
values that are received on serverside are already byte arrays.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:07 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-1267) IsMarshallableInterceptor causes unnecessary marshalling in remote access mode
[
https://issues.jboss.org/browse/ISPN-1267?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-1267:
-----------------------------------
Attachment: JProfiler Call tree view not showing calls.jpg
IsMarshallableInterceptor causes unnecessary marshalling in remote
access mode
------------------------------------------------------------------------------
Key: ISPN-1267
URL: https://issues.jboss.org/browse/ISPN-1267
Project: Infinispan
Issue Type: Bug
Components: Marshalling
Affects Versions: 5.0.0.CR8
Reporter: Michal Linhard
Assignee: Galder Zamarreño
Fix For: 5.0.0.FINAL
Attachments: JProfiler Call tree view not showing calls.jpg
this is because by default GenericJBossMarshaller is used and
GenericJBossMarshaller.isMarshallable implementation marshalls objects to find whether
they are marshallable.
this proves to be a very significant performance bottleneck, see details in JBPAPP-6865
in remote access storeAsBinary shouldn't have any performance impact, because the
values that are received on serverside are already byte arrays.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:10 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-1267) IsMarshallableInterceptor causes unnecessary marshalling in remote access mode
[
https://issues.jboss.org/browse/ISPN-1267?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-1267:
-----------------------------------
Attachment: Call graph looks fine though.jpg
IsMarshallableInterceptor causes unnecessary marshalling in remote
access mode
------------------------------------------------------------------------------
Key: ISPN-1267
URL: https://issues.jboss.org/browse/ISPN-1267
Project: Infinispan
Issue Type: Bug
Components: Marshalling
Affects Versions: 5.0.0.CR8
Reporter: Michal Linhard
Assignee: Galder Zamarreño
Fix For: 5.0.0.FINAL
Attachments: Call graph looks fine though.jpg, JProfiler Call tree view not
showing calls.jpg
this is because by default GenericJBossMarshaller is used and
GenericJBossMarshaller.isMarshallable implementation marshalls objects to find whether
they are marshallable.
this proves to be a very significant performance bottleneck, see details in JBPAPP-6865
in remote access storeAsBinary shouldn't have any performance impact, because the
values that are received on serverside are already byte arrays.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:13 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-1267) IsMarshallableInterceptor causes unnecessary marshalling in remote access mode
[
https://issues.jboss.org/browse/ISPN-1267?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-1267:
----------------------------------------
Apparently the call tree looks fine with JProfiler 6.2.2 though.
IsMarshallableInterceptor causes unnecessary marshalling in remote
access mode
------------------------------------------------------------------------------
Key: ISPN-1267
URL: https://issues.jboss.org/browse/ISPN-1267
Project: Infinispan
Issue Type: Bug
Components: Marshalling
Affects Versions: 5.0.0.CR8
Reporter: Michal Linhard
Assignee: Galder Zamarreño
Fix For: 5.0.0.FINAL
Attachments: Call graph looks fine though.jpg, JProfiler Call tree view not
showing calls.jpg
this is because by default GenericJBossMarshaller is used and
GenericJBossMarshaller.isMarshallable implementation marshalls objects to find whether
they are marshallable.
this proves to be a very significant performance bottleneck, see details in JBPAPP-6865
in remote access storeAsBinary shouldn't have any performance impact, because the
values that are received on serverside are already byte arrays.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:22 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-1267) IsMarshallableInterceptor causes unnecessary marshalling in remote access mode
[
https://issues.jboss.org/browse/ISPN-1267?page=com.atlassian.jira.plugin....
]
Michal Linhard updated ISPN-1267:
---------------------------------
Attachment: snap_put.png
snap_get.png
IsMarshallableInterceptor causes unnecessary marshalling in remote
access mode
------------------------------------------------------------------------------
Key: ISPN-1267
URL: https://issues.jboss.org/browse/ISPN-1267
Project: Infinispan
Issue Type: Bug
Components: Marshalling
Affects Versions: 5.0.0.CR8
Reporter: Michal Linhard
Assignee: Galder Zamarreño
Fix For: 5.0.0.FINAL
Attachments: Call graph looks fine though.jpg, JProfiler Call tree view not
showing calls.jpg, snap_get.png, snap_put.png
this is because by default GenericJBossMarshaller is used and
GenericJBossMarshaller.isMarshallable implementation marshalls objects to find whether
they are marshallable.
this proves to be a very significant performance bottleneck, see details in JBPAPP-6865
in remote access storeAsBinary shouldn't have any performance impact, because the
values that are received on serverside are already byte arrays.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:53 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-1267) Infinispan servers should disable storeAsBinary/lazyDeserialization
[
https://issues.jboss.org/browse/ISPN-1267?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-1267:
-----------------------------------
Summary: Infinispan servers should disable storeAsBinary/lazyDeserialization (was:
IsMarshallableInterceptor causes unnecessary marshalling in remote access mode)
Infinispan servers should disable storeAsBinary/lazyDeserialization
-------------------------------------------------------------------
Key: ISPN-1267
URL: https://issues.jboss.org/browse/ISPN-1267
Project: Infinispan
Issue Type: Bug
Components: Marshalling
Affects Versions: 5.0.0.CR8
Reporter: Michal Linhard
Assignee: Galder Zamarreño
Fix For: 5.0.0.FINAL
Attachments: Call graph looks fine though.jpg, JProfiler Call tree view not
showing calls.jpg, snap_get.png, snap_put.png
this is because by default GenericJBossMarshaller is used and
GenericJBossMarshaller.isMarshallable implementation marshalls objects to find whether
they are marshallable.
this proves to be a very significant performance bottleneck, see details in JBPAPP-6865
in remote access storeAsBinary shouldn't have any performance impact, because the
values that are received on serverside are already byte arrays.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:40 a.m.
New subject: [JBoss JIRA] Work started: (ISPN-1267) Infinispan servers should disable storeAsBinary/lazyDeserialization
[
https://issues.jboss.org/browse/ISPN-1267?page=com.atlassian.jira.plugin....
]
Work on ISPN-1267 started by Galder Zamarreño.
Infinispan servers should disable storeAsBinary/lazyDeserialization
-------------------------------------------------------------------
Key: ISPN-1267
URL: https://issues.jboss.org/browse/ISPN-1267
Project: Infinispan
Issue Type: Bug
Components: Marshalling
Affects Versions: 5.0.0.CR8
Reporter: Michal Linhard
Assignee: Galder Zamarreño
Fix For: 5.0.0.FINAL
Attachments: Call graph looks fine though.jpg, JProfiler Call tree view not
showing calls.jpg, snap_get.png, snap_put.png
this is because by default GenericJBossMarshaller is used and
GenericJBossMarshaller.isMarshallable implementation marshalls objects to find whether
they are marshallable.
this proves to be a very significant performance bottleneck, see details in JBPAPP-6865
in remote access storeAsBinary shouldn't have any performance impact, because the
values that are received on serverside are already byte arrays.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:06 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-1267) Infinispan servers should disable storeAsBinary/lazyDeserialization
[
https://issues.jboss.org/browse/ISPN-1267?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-1267:
-----------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/infinispan/infinispan/pull/467
Infinispan servers should disable storeAsBinary/lazyDeserialization
-------------------------------------------------------------------
Key: ISPN-1267
URL: https://issues.jboss.org/browse/ISPN-1267
Project: Infinispan
Issue Type: Bug
Components: Marshalling
Affects Versions: 5.0.0.CR8
Reporter: Michal Linhard
Assignee: Galder Zamarreño
Fix For: 5.0.0.FINAL
Attachments: Call graph looks fine though.jpg, JProfiler Call tree view not
showing calls.jpg, snap_get.png, snap_put.png
this is because by default GenericJBossMarshaller is used and
GenericJBossMarshaller.isMarshallable implementation marshalls objects to find whether
they are marshallable.
this proves to be a very significant performance bottleneck, see details in JBPAPP-6865
in remote access storeAsBinary shouldn't have any performance impact, because the
values that are received on serverside are already byte arrays.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:43 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-1267) Infinispan servers should disable storeAsBinary/lazyDeserialization
[
https://issues.jboss.org/browse/ISPN-1267?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-1267:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
integrated
Infinispan servers should disable storeAsBinary/lazyDeserialization
-------------------------------------------------------------------
Key: ISPN-1267
URL: https://issues.jboss.org/browse/ISPN-1267
Project: Infinispan
Issue Type: Bug
Components: Marshalling
Affects Versions: 5.0.0.CR8
Reporter: Michal Linhard
Assignee: Galder Zamarreño
Fix For: 5.0.0.FINAL
Attachments: Call graph looks fine though.jpg, JProfiler Call tree view not
showing calls.jpg, snap_get.png, snap_put.png
this is because by default GenericJBossMarshaller is used and
GenericJBossMarshaller.isMarshallable implementation marshalls objects to find whether
they are marshallable.
this proves to be a very significant performance bottleneck, see details in JBPAPP-6865
in remote access storeAsBinary shouldn't have any performance impact, because the
values that are received on serverside are already byte arrays.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:33 a.m.
New subject: [JBoss JIRA] Reopened: (ISPN-1267) Infinispan servers should disable storeAsBinary/lazyDeserialization
[
https://issues.jboss.org/browse/ISPN-1267?page=com.atlassian.jira.plugin....
]
Galder Zamarreño reopened ISPN-1267:
------------------------------------
As indicated in JBPAPP-6918, caches in AS7 might be started before the Hot Rod server is
started, so a different approach is needed here.
Infinispan servers should disable storeAsBinary/lazyDeserialization
-------------------------------------------------------------------
Key: ISPN-1267
URL: https://issues.jboss.org/browse/ISPN-1267
Project: Infinispan
Issue Type: Bug
Components: Marshalling
Affects Versions: 5.0.0.CR8
Reporter: Michal Linhard
Assignee: Galder Zamarreño
Fix For: 5.0.0.FINAL
Attachments: Call graph looks fine though.jpg, JProfiler Call tree view not
showing calls.jpg, snap_get.png, snap_put.png
this is because by default GenericJBossMarshaller is used and
GenericJBossMarshaller.isMarshallable implementation marshalls objects to find whether
they are marshallable.
this proves to be a very significant performance bottleneck, see details in JBPAPP-6865
in remote access storeAsBinary shouldn't have any performance impact, because the
values that are received on serverside are already byte arrays.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:23 p.m.
New subject: [JBoss JIRA] Commented: (ISPN-1267) Infinispan servers should disable storeAsBinary/lazyDeserialization
[
https://issues.jboss.org/browse/ISPN-1267?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-1267:
----------------------------------------
Taking advantage of the lifecycle callback cacheStarting() solves the issue in a couple of
lines, much better than the previous solution :)
Infinispan servers should disable storeAsBinary/lazyDeserialization
-------------------------------------------------------------------
Key: ISPN-1267
URL: https://issues.jboss.org/browse/ISPN-1267
Project: Infinispan
Issue Type: Bug
Components: Marshalling
Affects Versions: 5.0.0.CR8
Reporter: Michal Linhard
Assignee: Galder Zamarreño
Fix For: 5.0.0.FINAL
Attachments: Call graph looks fine though.jpg, JProfiler Call tree view not
showing calls.jpg, snap_get.png, snap_put.png
this is because by default GenericJBossMarshaller is used and
GenericJBossMarshaller.isMarshallable implementation marshalls objects to find whether
they are marshallable.
this proves to be a very significant performance bottleneck, see details in JBPAPP-6865
in remote access storeAsBinary shouldn't have any performance impact, because the
values that are received on serverside are already byte arrays.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:26 p.m.
New subject: [JBoss JIRA] Updated: (ISPN-1267) Infinispan servers should disable storeAsBinary/lazyDeserialization
[
https://issues.jboss.org/browse/ISPN-1267?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-1267:
-----------------------------------
Status: Pull Request Sent (was: Reopened)
Git Pull Request: https://github.com/infinispan/infinispan/pull/467,
https://github.com/infinispan/infinispan/pull/473 (was:
https://github.com/infinispan/infinispan/pull/467)
Infinispan servers should disable storeAsBinary/lazyDeserialization
-------------------------------------------------------------------
Key: ISPN-1267
URL: https://issues.jboss.org/browse/ISPN-1267
Project: Infinispan
Issue Type: Bug
Components: Marshalling
Affects Versions: 5.0.0.CR8
Reporter: Michal Linhard
Assignee: Galder Zamarreño
Fix For: 5.0.0.FINAL
Attachments: Call graph looks fine though.jpg, JProfiler Call tree view not
showing calls.jpg, snap_get.png, snap_put.png
this is because by default GenericJBossMarshaller is used and
GenericJBossMarshaller.isMarshallable implementation marshalls objects to find whether
they are marshallable.
this proves to be a very significant performance bottleneck, see details in JBPAPP-6865
in remote access storeAsBinary shouldn't have any performance impact, because the
values that are received on serverside are already byte arrays.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:24 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-1267) Infinispan servers should disable storeAsBinary/lazyDeserialization
[
https://issues.jboss.org/browse/ISPN-1267?page=com.atlassian.jira.plugin....
]
Manik Surtani updated ISPN-1267:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
Infinispan servers should disable storeAsBinary/lazyDeserialization
-------------------------------------------------------------------
Key: ISPN-1267
URL: https://issues.jboss.org/browse/ISPN-1267
Project: Infinispan
Issue Type: Bug
Components: Marshalling
Affects Versions: 5.0.0.CR8
Reporter: Michal Linhard
Assignee: Galder Zamarreño
Fix For: 5.0.0.FINAL
Attachments: Call graph looks fine though.jpg, JProfiler Call tree view not
showing calls.jpg, snap_get.png, snap_put.png
this is because by default GenericJBossMarshaller is used and
GenericJBossMarshaller.isMarshallable implementation marshalls objects to find whether
they are marshallable.
this proves to be a very significant performance bottleneck, see details in JBPAPP-6865
in remote access storeAsBinary shouldn't have any performance impact, because the
values that are received on serverside are already byte arrays.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4896
days inactive
4903
days old
infinispan-issues@lists.jboss.org
17 comments
4 participants
participants (4)
-
Galder Zamarreño (JIRA) -
Manik Surtani (JIRA)
-
Michal Linhard (JIRA)
-
Mircea Markus (JIRA)