Ok from my side.
Few more details about tracing spi updates, based on mentioned above
discussion with Nikolay and Nikita.
Tracing provides enough data for a performance profiling tool, actually
only root spans are required. However, according to Nikinta,
root-span-tracing has a 7-8% performance
Guys,
I have filed the ticket [1] to improve the TracingSpi interface and
further reusing it for cluster profiling. I'll assign it to me and
take it to work after profiling merge if nobody minds.
[1] https://issues.apache.org/jira/browse/IGNITE-13850
пн, 14 дек. 2020 г. в 13:38, Alexander Lapin
Kirill Tkalenko created IGNITE-13848:
Summary: Premature update SegmentReservationStorage#minReserveIdx
during truncate of segments
Key: IGNITE-13848
URL: https://issues.apache.org/jira/browse/IGNITE-13848
Taras Ledkov created IGNITE-13849:
-
Summary: Calcite Integration. Add unit tests for all IgniteRel
nodes serialization / deserialization
Key: IGNITE-13849
URL: https://issues.apache.org/jira/browse/IGNITE-13849
Amelchev Nikita created IGNITE-13850:
Summary: Improve the TracingSpi interface
Key: IGNITE-13850
URL: https://issues.apache.org/jira/browse/IGNITE-13850
Project: Ignite
Issue Type:
Hello, Igniters.
We discussed this feature privately with Alexander and Nikita.
Here are the results we want to share with the community:
0. In the end, both, performance statistic tool and tracing should use the same
API.
1. We should improve the Tracing API, so it able to be used for
Ilya Kasnacheev created IGNITE-13851:
Summary: Document persistence forward compatibility policy
Key: IGNITE-13851
URL: https://issues.apache.org/jira/browse/IGNITE-13851
Project: Ignite
vveider closed pull request #7:
URL: https://github.com/apache/ignite-3/pull/7
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the
vveider opened a new pull request #7:
URL: https://github.com/apache/ignite-3/pull/7
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go
So just one bit to consider... Are there features that you need to use in these
newer versions of java? Or are we just updating to stay current? The reason I
ask is that there are still lots of people in an enterprise space that are
beholden to having to support legacy JAVAEE supported
Amelchev Nikita created IGNITE-13854:
Summary: Add documentation for the cluster performance profiling
tool
Key: IGNITE-13854
URL: https://issues.apache.org/jira/browse/IGNITE-13854
Project:
Denis A. Magda created IGNITE-13853:
---
Summary: Add APIs, examples, language selector to the docs menu
Key: IGNITE-13853
URL: https://issues.apache.org/jira/browse/IGNITE-13853
Project: Ignite
Kirill Gusakov created IGNITE-13852:
---
Summary: Ascii tables for new unified cli tool
Key: IGNITE-13852
URL: https://issues.apache.org/jira/browse/IGNITE-13852
Project: Ignite
Issue Type:
Dear Community,
I have uploaded release candidate to
https://dist.apache.org/repos/dist/dev/ignite/2.9.1-rc1/
https://dist.apache.org/repos/dist/dev/ignite/packages_2.9.1-rc1/
The following staging can be used for testing:
https://repository.apache.org/content/repositories/orgapacheignite-1490/
+1
--
Regards,
Konstantin Orlov
Software Engineer, St. Petersburg
+7 (921) 445-65-75
https://www.gridgain.com
Powered by Apache® Ignite™
15 matches
Mail list logo
