Tuesday, August 5, 2014

Re: vim 7.4: pasting is very slow on HP UX machine.

On Tuesday, 1 July 2014 14:23:22 UTC-4, Christian Brabandt wrote:
> Hi
>
>
>
> On Di, 01 Jul 2014, KKde wrote:
>
>
>
> > >
>
> > > Since you already recompiled your Vim, would it be hard for you to
>
> > > profile it?
>
> > >
>
> > > That might give us a clue, what is going on.
>
> >
>
> > What flags I should use for profiling?
>
>
>
> Seriously I do not know. I would start with uncommenting the
>
> PROFILE_LIBS variable in the Makefile and see how that works...
>
>
>
> Last time I did this, I think, I used the
>
> http://www.thegeekstuff.com/2012/08/gprof-tutorial/ to profile Vim.
>
>
>
> e.g. export PROFILE_LIBS = -pg, compile and then
>
> run a slow operation with the new compiled vim and use gprof gmon.out
>
> and from there look at the most obvious slow down function calls.
>
>
>
> On Windows, I would just compile a debug version and use ltprof.
>
>
>
> Best,
>
> Christian
>
> --
>
> Wie man sein Kind nicht nennen sollte:
>
> Karl Ender

Hi,

Below are the profiling stats on two machines A & B. On machine B it is working fine. Both machines are HPUX only

%Time Seconds Cumsecs #Calls msec/call Name

MACHINE A

27.8 0.05 0.05 1490 0.03 do_cmdline
5.6 0.01 0.06 77666 0.00 hash_lookup
5.6 0.01 0.07 24190 0.00 find_special_key
5.6 0.01 0.08 11503 0.00 separate_nextcmd
5.6 0.01 0.09 396 0.03 do_map
0.0 0.00 0.09 463530 0.00 skipwhite
0.0 0.00 0.09 348653 0.00 vim_strchr
0.0 0.00 0.09 209196 0.00 vim_free
0.0 0.00 0.09 162231 0.00 vim_isIDc
0.0 0.00 0.09 124661 0.00 getline_equal



MACHINE B
%Time Seconds Cumsecs #Calls msec/call Name

15.4 0.02 0.02 442611 0.00 skipwhite
7.7 0.01 0.03 77397 0.00 hash_lookup
7.7 0.01 0.04 13131 0.00 vim_str2nr
7.7 0.01 0.05 4588 0.00 dbg_check_skipped
0.0 0.00 0.05 253469 0.00 vim_strchr
0.0 0.00 0.05 183319 0.00 vim_free
0.0 0.00 0.05 152910 0.00 vim_isIDc
0.0 0.00 0.05 116353 0.00 getline_equal
0.0 0.00 0.05 69606 0.00 hash_find
0.0 0.00 0.05 67704 0.00 dict_unref

do_cmdline, find_special_key, separate_nextcmd, do_map functions are taking long time.

Can anyone tell why these functions are taking long time?

Regards,
Sarath

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment