On 11 January 2013 03:12, wrote:
> Hi Xiao Feng,
>
>
> The line which is getting slower with time is highlighted in yellow, below.
>
>
>
> On Friday, January 11, 2013 4:31:46 PM UTC+5:30, Feng Xiao wrote:
>>
>>
>> [adding back the group]
>>
>> On Fri, Jan 11, 2013 at 5:53 PM, Debopam Ghoshal
>>
Hi Xiao Feng,
The line which is getting slower with time is highlighted in yellow, below.
On Friday, January 11, 2013 4:31:46 PM UTC+5:30, Feng Xiao wrote:
>
>
> [adding back the group]
>
> On Fri, Jan 11, 2013 at 5:53 PM, Debopam Ghoshal
>
> > wrote:
>
>> Hi Xiao Feng, please find below the
[adding back the group]
On Fri, Jan 11, 2013 at 5:53 PM, Debopam Ghoshal wrote:
> Hi Xiao Feng, please find below the relevant sections of my applications
> code:
>
> This is the point where Apache MINA receives the request from the client.
> The MultiRequest is a generated class from the protob
ohhh... AIX..
oprofile & latencytop is for Linux only :(
so. If i understand correctly
-- You know that slowdown you are interesting lay in protobuf
-- all other [network / request data size / request complexity ] is the
same at the start and after the week
from my exp [oh, also very limited] AI
Thanks for your suggestions. Please find my response below:
On Friday, January 11, 2013 1:16:19 PM UTC+5:30, Дмитрий Дьяченко wrote:
>
> if i undestand correctly, You have a looong-run application.
>
Yes, you are right, my application is a really long running one. It is
expected to run 24 x
At present I do not have a short and running example code for this. Also,
the received request object is not getting larges (it is never more than
250KB). I did some memory profiling, but did not find any irregularities
over there.
I am using JDK 6.
On Friday, January 11, 2013 1:15:56 PM UTC+
Initially I also thought that the problem lies in the garbage collector
(your assumption is correct, I am using JVM), or memory leakage. However, I
have been monitoring the application's memory and thread profiles (using
JConsole), but found no irregularities.
I also agree with you that there i
if i undestand correctly, You have a looong-run application.
- at start You have 2 ms cycle request-response
- after a week You have 200 ms cycle
- Your app is correct and only place where problem may lay is protobuf?
can You do the following?
-- run 'latencytop' at start and after a week?
-- run
On Friday, January 11, 2013 3:30:26 PM UTC+8, debo...@2pirad.com wrote:
>
> Because, to process the request object (in #7), the methods which are
> present in the google protobuf generated file are called. The protobuf
> request object contains multiple requests, and the time taken to extract
On 10 January 2013 23:30, wrote:
> Because, to process the request object (in #7), the methods which are
> present in the google protobuf generated file are called. The protobuf
> request object contains multiple requests, and the time taken to extract
> these (requests) is gradually increasing w
Because, to process the request object (in #7), the methods which are
present in the google protobuf generated file are called. The protobuf
request object contains multiple requests, and the time taken to extract
these (requests) is gradually increasing with time.
I think this is protobuf prob
What makes you think it's protobuf's problem?
On Friday, January 11, 2013 2:50:54 PM UTC+8, debo...@2pirad.com wrote:
>
> My application uses Google Protocol Buffer with Apache MINA. There are
> clients who connect to the MINA Connector, send request to the server and
> then wait for the respons
12 matches
Mail list logo
