my own fault. Thanks for
> making me have a look at that again.
>
> Thanks,
> Brett
>
> -Original Message-
> From: Igor Sapego [mailto:isap...@apache.org]
> Sent: Tuesday, September 29, 2020 2:22 AM
> To: dev
> Subject: [EXTERNAL] Re: cpp thin client vector resi
: Tuesday, September 29, 2020 2:22 AM
To: dev
Subject: [EXTERNAL] Re: cpp thin client vector resize
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you recognize the sender and know the content
is safe.
Hi,
Can you share your ignite
I believe the vector itself should not be a problem. So there is no point
in changing
std::vector to anything else. It is possible though that there is a problem
with code
that deals with the vector.
Also it would help though not necessary if you could provide profiling
results.
Best Regards,
Hi,
Can you share your ignite::binary::BinaryType::Read method where reading of
the std::vector is going on?
Also, are your strings large too or only vectors?
Best Regards,
Igor
On Mon, Sep 28, 2020 at 8:29 PM Brett Elliott wrote:
> Hello,
>
> Tl;dr: I'm doing some profiling, and the cpp
Hello,
Tl;dr: I'm doing some profiling, and the cpp thin client is spending a lot of
time in memset. It's spending almost as much time as in the socket recv call.
Longer version:
I was profiling a test harness that does a Get from our ingite grid. The test
harness is written in c++ using the
