Hi Val,
I'm sorry, of course only @QuerySqlField(index = true) makes an index on
objects field. Fields without indexes make none additional overhead.
Group index on multiple fields is a one index (isn't it?)
I don't understand what is still unclear.
Entry footprint = key footprint + value foot
Alexandr,
See my comments below.
On Wed, Dec 21, 2016 at 7:01 PM, Alexandr Kuramshin
wrote:
> Hi Val,
>
> the understanding is simple.
>
> When you enables the single index on entry class you get "First index
> overhead" per entry.
>
> When you enables two indices on entry class you get "First
Hi Val,
the understanding is simple.
When you enables the single index on entry class you get "First index
overhead" per entry.
When you enables two indices on entry class you get "First index overhead"
+ "Next index overhead" per entry.
With three indices you get "First index overhead" + 2 * "
This is the documentation domain that has been left historically. In general,
Ignite was contributed to Apache by GridGain a couple of years ago and now
GridGain provides additional enterprise level features on top of Ignite.
The valid link to the doc is:
https://apacheignite.readme.io/docs/capa
What is the relationship of apacheignite.gridgain.org to the open source
Apache Ignite project? Thanks!
On Tue, Dec 13, 2016 at 2:37 AM, Alexandr Kuramshin
wrote:
> Hello, Igniters,
>
> I'd like to represent updated article [1] about the subject.
>
> And I'll very appreciate your comments and qu
Alexandr,
Can you please clarify what is "First index overhead" and "Next index
overhead"? Generally, I think overhead provided by indexes should be
described in more details, now it's not very clear what happens when
indexes are added.
Also the calculation example should be a separate section.
Thank you, Andrey,
I'll do additional tests with expire policy and update the article.
2016-12-13 22:10 GMT+07:00 Andrey Mashenkov :
> Alexandr,
>
> In addition. If expire policy is configured, there is additional overhead
> to entries can be tracked by TtlManager.
> This overhead is OnHeap and
Alexandr,
In addition. If expire policy is configured, there is additional overhead
to entries can be tracked by TtlManager.
This overhead is OnHeap and does not depend on cache MemoryMode (until
Ignite-3840 will be in master).
For now overhead is about 32-40 bytes (EntryWrapper itself) + (40-48)
Alexander, great update, thanks.
Yakov, Alexey Scherbakov, Val,
Please do the review first since you’re as the ones who deal a lot with
performance and memory usage related questions.
—
Denis
> On Dec 12, 2016, at 11:37 PM, Alexandr Kuramshin wrote:
>
> Hello, Igniters,
>
> I'd like to rep
Hello, Igniters,
I'd like to represent updated article [1] about the subject.
And I'll very appreciate your comments and questions about it.
Please review.
[1] http://apacheignite.gridgain.org/docs/capacity-planning
--
Thanks,
Alexandr Kuramshin
10 matches
Mail list logo
