TeamForge : Post

Forum Topic - Latency: (7 Items)

View: as

Mario Charest

06/02/2008 1:40 PM

post8657

I`m testing the Photon version of Tau.  

When I launch a build ( custom Makefile ). It takes the IDE about 10 seconds to realized the makefile is done.  That 
means 10 extra seconds before the error are parsed and display.

Anyway to get rid of this?

Elena Laskavaia

06/02/2008 3:25 PM

post8663

Re: Latency

Well parsing of makefiles takes these extra 10 seconds. You can turn off 
parsing and it will be faster but you won't have errors in the problems 
view.

Mario Charest wrote:
> I`m testing the Photon version of Tau.  
>
> When I launch a build ( custom Makefile ). It takes the IDE about 10
seconds to realized the makefile is done.  That means 10 extra seconds
before the error are parsed and display.
>
> Anyway to get rid of this?
>
>
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post8657
>
>

Mario Charest

06/02/2008 4:18 PM

post8664

Re: Latency

> Well parsing of makefiles takes these extra 10 seconds. You can turn off 
> parsing and it will be faster but you won't have errors in the problems 
> view.

That can`t be right.  The output is about 5 lines, that`s 2 seconds per line...   

I made a small change so that a make clean doesn`t output anything at all.  Yet it still takes 10 seconds.  During this 
10 seconds in the status bar I can see "Building targets.: (0%)".  During this 10 seconds there is about 20% of the 
processor used by devb-eide and 30% by pvm.

More investigation:  The project is made up of multiple sub-directory which all have their own makefile. It seems that 
when I launch a make  in a sub-directory after it`s done build it, it ends up scanning files in the whole project.  I 
caught these with pidin fd. Maybe it`s looking for binaries ?

> 
> Mario Charest wrote:
> > I`m testing the Photon version of Tau.  
> >
> > When I launch a build ( custom Makefile ). It takes the IDE about 10
> seconds to realized the makefile is done.  That means 10 extra seconds
> before the error are parsed and display.
> >
> > Anyway to get rid of this?
> >
> >
> > _______________________________________________
> > General
> > http://community.qnx.com/sf/go/post8657
> >
> >

Elena Laskavaia

06/02/2008 5:46 PM

post8665

Re: Latency

Yeah this is true. It is doing refresh after the build to pick up new 
binaries, maybe this takes lots of time.
You can try to run pvm with enabled jit (optimized bytecode), it would 
take a LOT time to start up but it suppose to be faster after that.
To start with jit remove option -nojit from qde.ini file

Mario Charest wrote:
>> Well parsing of makefiles takes these extra 10 seconds. You can turn off 
>> parsing and it will be faster but you won't have errors in the problems 
>> view.
>>     
>
> That can`t be right.  The output is about 5 lines, that`s 2 seconds per
line...   
>
> I made a small change so that a make clean doesn`t output anything at all.
Yet it still takes 10 seconds.  During this 10 seconds in the status bar I
can see "Building targets.: (0%)".  During this 10 seconds there is about
20% of the processor used by devb-eide and 30% by pvm.
>
> More investigation:  The project is made up of multiple sub-directory
which all have their own makefile. It seems that when I launch a make  in a
sub-directory after it`s done build it, it ends up scanning files in the
whole project.  I caught these with pidin fd. Maybe it`s looking for
binaries ?
>
>   
>> Mario Charest wrote:
>>     
>>> I`m testing the Photon version of Tau.  
>>>
>>> When I launch a build ( custom Makefile ). It takes the IDE about 10
>>>       
>> seconds to realized the makefile is done.  That means 10 extra seconds
>> before the error are parsed and display.
>>     
>>> Anyway to get rid of this?
>>>
>>>
>>> _______________________________________________
>>> General
>>> http://community.qnx.com/sf/go/post8657
>>>
>>>   
>>>       
>
>
>
>
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post8664
>
>

Mario Charest

06/03/2008 4:21 PM

post8724

Re: Latency

> Yeah this is true. It is doing refresh after the build to pick up new 
> binaries, maybe this takes lots of time.
> You can try to run pvm with enabled jit (optimized bytecode), it would 
> take a LOT time to start up but it suppose to be faster after that.
> To start with jit remove option -nojit from qde.ini file

Nah still too slow.  I wanted to see if removing -nojit made some operation faster, I tried a search/File, didn't work 
at all.  Seems like it's not doing anything.

That being said the overall performance is not up to par with the Windows version so I'm not going to spend any more 
time on the self hosted version of Eclipse for now.

Mario Charest

07/09/2008 2:31 PM

post10273

Re: Latency

> > Yeah this is true. It is doing refresh after the build to pick up new 
> > binaries, maybe this takes lots of time.

I have the same problem under Windows. Any way to disable the scanning of binary after the custom makefile has returned?

Elena Laskavaia

07/09/2008 2:49 PM

post10274

Re: Latency

If there is any preference about it, they would be in 
Windows->Preferences, type Refresh in filter box.
I could not find anything related to "Refresh after build". You can ask 
on cdt newsgroup.

Mario Charest wrote:
>>> Yeah this is true. It is doing refresh after the build to pick up new 
>>> binaries, maybe this takes lots of time.
>>>       
>
> I have the same problem under Windows. Any way to disable the scanning of binary after the custom makefile has 
returned?
>
>
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post10273
>
>

Return