Sponsored Content
The Lounge What is on Your Mind? Similar Threads for Man Pages - In Development Post 303042560 by Neo on Sunday 29th of December 2019 08:59:08 PM
Old 12-29-2019
Step 3 is done. The result is that the orphans have dropped from 63% to 53%.

Code:
mysql> select count(1) as count from neo_man_page_entry where similarthread = "notagsmatch"; select count(1) as count from neo_man_page_entry;
+--------+
| count  |
+--------+
| 185765 |
+--------+
1 row in set (0.93 sec)

+--------+
| count  |
+--------+
| 347938 |
+--------+
1 row in set (0.00 sec)

So, I now start step 4:

STEP4: Boolean Matches Man Page Name with Post Text

I will take the remaining man pages without any similar threads and repeat step three but matching the name of the man page (only the query, for example 'sshd') against the page text for each post and get the threadid from the post, and order the matches by the number of times the thread was thanked by users, and keep up to 15 matches, as before.

We will see how many man page orphans find thread relatives in this step 4 manner.

Running...... looks like this query and update will take around a week or so, as not to overload the server.

Code:
1577672816 Time: 54 Inserts: 6 Floor: 6000 Limit: 20 ToDo: 185205 RemainingTime: 154.3 Hours QLoad: 1.65
1577672876 Time: 52 Inserts: 4 Floor: 6000 Limit: 20 ToDo: 185185 RemainingTime: 154.3 Hours QLoad: 1.53
1577672942 Time: 54 Inserts: 1 Floor: 6000 Limit: 20 ToDo: 185165 RemainingTime: 154.3 Hours QLoad: 1.04
1577673000 Time: 53 Inserts: 0 Floor: 6000 Limit: 20 ToDo: 185145 RemainingTime: 154.3 Hours QLoad: 1.20

.and so far, it looks like the orphans will be only reduced by a relatively small amount (less than 15% of total remaining orphans, I guess... let's see)
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Man pages

Hello , I just installed openssh in my system . I actually tried to man sshd but it says no entry , though there is a man directory in the installation which have the man pages for sshd . Can anyone tell me how should i install these man pages . DP (2 Replies)
Discussion started by: DPAI
2 Replies

2. UNIX for Dummies Questions & Answers

man pages

Hi, I've written now a man pages, but I don't knwo how to get 'man' to view them. Where have I to put this files, which directories are allowed?? THX Bensky (3 Replies)
Discussion started by: bensky
3 Replies

3. UNIX for Dummies Questions & Answers

man pages

Hi folks, I want to know all the commands for which man pages are available. How do i get it? Cheers, Nisha (4 Replies)
Discussion started by: Nisha
4 Replies

4. UNIX for Dummies Questions & Answers

man pages

When reading man pages, I notice that sometimes commands are follwed by a number enclosed in parenthesis. such as: mkdir calls the mkdir(2) system call. What exactly does this mean? (4 Replies)
Discussion started by: dangral
4 Replies

5. UNIX for Dummies Questions & Answers

how to read man pages

can anybody explain me how to read unix man pages? for example when i want to get information about ps command man ps gives me this output: *********************************** Reformatting page. Please wait... completed ps(1) ... (2 Replies)
Discussion started by: gfhgfnhhn
2 Replies

6. UNIX for Dummies Questions & Answers

Man pages on Solaris 10

Hi, I want to install man pages package from solaris 10. Solaris 10 has already been installed on my servor but I have to add the man pages packages. I search for a long time on internet this package but I didn't find a compatible one... So I downloaded Solaris 10 from Sun site to get this... (1 Reply)
Discussion started by: MasterapocA
1 Replies

7. Fedora

why do we have .1 extension in MAN PAGES?

Hello sir, I am using FEDORA 9. I wanted to know why do we have ".1" extension in the archives of man pages. I know we are giving format. I want to know the importance or purpose of this format. Can you please tell me :confused: (2 Replies)
Discussion started by: nsharath
2 Replies

8. Solaris

MAN PAGES

Hi everyone, I have a small query, in solaris the man pages get displayed on half of the terminal , can i get a full terminal or full screen display ?:) (2 Replies)
Discussion started by: M.Choudhury
2 Replies

9. HP-UX

Looking for some man pages.

Can anyone supply me with the man pages for: omnidatalist omnibarlist omnisap.exe I prefer the source man pages in nroff format. A clue about the software bundles which supply these man pages is fine as well. OS: HP-UX TIA (11 Replies)
Discussion started by: sb008
11 Replies

10. Shell Programming and Scripting

Commands for man pages

what command should i use for displaying the manual pages for the socket, read and connect system calls? (1 Reply)
Discussion started by: Nabeel Nazir
1 Replies
cprof(3erl)						     Erlang Module Definition						       cprof(3erl)

NAME
cprof - A simple Call Count Profiling Tool using breakpoints for minimal runtime performance impact. DESCRIPTION
The cprof module is used to profile a program to find out how many times different functions are called. Breakpoints similar to local call trace, but containing a counter, are used to minimise runtime performance impact. Since breakpoints are used there is no need for special compilation of any module to be profiled. For now these breakpoints can only be set on BEAM code so s cannot be call count traced. The size of the call counters is the host machine word size. One bit is used when pausing the counter, so the maximum counter value for a 32-bit host is 2147483647. The profiling result is delivered as a term containing a sorted list of entries, one per module. Each module entry contains a sorted list of functions. The sorting order in both cases is of decreasing call count. Call count tracing is very lightweight compared to other forms of tracing since no trace message has to be generated. Some measurements indicates performance degradation in the vicinity of 10 percent. EXPORTS
analyse() -> {AllCallCount, ModAnalysisList} analyse(Limit) -> {AllCallCount, ModAnalysisList} analyse(Mod) -> ModAnlysis analyse(Mod, Limit) -> ModAnalysis Types Limit = integer() Mod = atom() AllCallCount = integer() ModAnalysisList = [ModAnalysis] ModAnalysis = {Mod, ModCallCount, FuncAnalysisList} ModCallCount = integer() FuncAnalysisList = [{{Mod, Func, Arity}, FuncCallCount}] Func = atom() Arity = integer() FuncCallCount = integer() Collects and analyses the call counters presently in the node for either module Mod , or for all modules (except cprof itself), and returns: FuncAnalysisList : A list of tuples, one for each function in a module, in decreasing FuncCallCount order. ModCallCount : The sum of FuncCallCount values for all functions in module Mod . AllCallCount : The sum of ModCallCount values for all modules concerned in ModAnalysisList . ModAnalysisList : A list of tuples, one for each module except cprof , in decreasing ModCallCount order. If call counters are still running while analyse/0..2 is executing, you might get an inconsistent result. This happens if the process executing analyse/0..2 gets scheduled out so some other process can increment the counters that are being analysed, Calling pause() before analysing takes care of the problem. If the Mod argument is given, the result contains a ModAnalysis tuple for module Mod only, otherwise the result contains one Mod- Analysis tuple for all modules returned from code:all_loaded() except cprof itself. All functions with a FuncCallCount lower than Limit are excluded from FuncAnalysisList . They are still included in ModCallCount , though. The default value for Limit is 1 . pause() -> integer() Pause call count tracing for all functions in all modules and stop it for all functions in modules to be loaded. This is the same as (pause({'_','_','_'})+stop({on_load})) . See also pause/1..3 below. pause(FuncSpec) -> integer() pause(Mod, Func) -> integer() pause(Mod, Func, Arity) -> integer() Types FuncSpec = Mod | {Mod,Func,Arity}, {FS} Mod = atom() Func = atom() Arity = integer() FS = term() Pause call counters for matching functions in matching modules. The FS argument can be used to specify the first argument to erlang:trace_pattern/3 . See erlang(3erl). The call counters for all matching functions that has got call count breakpoints are paused at their current count. Return the number of matching functions that can have call count breakpoints, the same as start/0..3 with the same arguments would have returned. restart() -> integer() restart(FuncSpec) -> integer() restart(Mod, Func) -> integer() restart(Mod, Func, Arity) -> integer() Types FuncSpec = Mod | {Mod,Func,Arity}, {FS} Mod = atom() Func = atom() Arity = integer() FS = term() Restart call counters for the matching functions in matching modules that are call count traced. The FS argument can be used to specify the first argument to erlang:trace_pattern/3 . See erlang(3erl). The call counters for all matching functions that has got call count breakpoints are set to zero and running. Return the number of matching functions that can have call count breakpoints, the same as start/0..3 with the same arguments would have returned. start() -> integer() Start call count tracing for all functions in all modules, and also for all functions in modules to be loaded. This is the same as (start({'_','_','_'})+start({on_load})) . See also start/1..3 below. start(FuncSpec) -> integer() start(Mod, Func) -> integer() start(Mod, Func, Arity) -> integer() Types FuncSpec = Mod | {Mod,Func,Arity}, {FS} Mod = atom() Func = atom() Arity = integer() FS = term() Start call count tracing for matching functions in matching modules. The FS argument can be used to specify the first argument to erlang:trace_pattern/3 , for example on_load . See erlang(3erl). Set call count breakpoints on the matching functions that has no call count breakpoints. Call counters are set to zero and running for all matching functions. Return the number of matching functions that has got call count breakpoints. stop() -> integer() Stop call count tracing for all functions in all modules, and also for all functions in modules to be loaded. This is the same as (stop({'_','_','_'})+stop({on_load})) . See also stop/1..3 below. stop(FuncSpec) -> integer() stop(Mod, Func) -> integer() stop(Mod, Func, Arity) -> integer() Types FuncSpec = Mod | {Mod,Func,Arity}, {FS} Mod = atom() Func = atom() Arity = integer() FS = term() Stop call count tracing for matching functions in matching modules. The FS argument can be used to specify the first argument to erlang:trace_pattern/3 , for example on_load . See erlang(3erl). Remove call count breakpoints from the matching functions that has call count breakpoints. Return the number of matching functions that can have call count breakpoints, the same as start/0..3 with the same arguments would have returned. SEE ALSO
eprof(3erl), fprof(3erl), erlang(3erl), User's Guide Ericsson AB tools 2.6.6.3 cprof(3erl)
All times are GMT -4. The time now is 05:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy