Sponsored Content
Top Forums Web Development Notes with Ravinder on Badging System Development Part II Post 303028271 by Neo on Thursday 3rd of January 2019 07:44:39 AM
Old 01-03-2019
I like your idea about a Mod issues badge to anyone who has posted some outstanding project or story. That badge can be nominated by a Mod and discussed in the Mod forum and when we approve it; I can add that user's userid to the array and it's done, easy.

Regarding, making a badge based on "getting a thanks within a week", the problem for that badge is that few people will achieve it and so that badge will remain "lightgray" forever for some number greater than 99% of the forum members and after a week passes, they will never have a chance to get that badge; so I think I'll pass on that one.. but that's for the idea!
 

3 More Discussions You Might Find Interesting

1. What is on Your Mind?

New Badging System - Badges Prototype Beta 1 (Badges Only)

Today I mapped out the new badging system using FA icons, Beta 1 in no particular order except a 6 x 8 grid: https://www.unix.com/members/1-albums215-picture991.png The prototype HTML code for this layout: <style> .fa-badge-grid { font-size: 1.5em; } .row { ... (38 Replies)
Discussion started by: Neo
38 Replies

2. What is on Your Mind?

Status of Badging System - Beta 1

Dear All, Here is the current status of the badging system: The Beta 1 phase of the new badging system is close to completion. 42 prototype badges have been "allocated" 6 prototype badge slots are held in reserve The "alert you have new badges" prototype is running and is currently... (4 Replies)
Discussion started by: Neo
4 Replies

3. What is on Your Mind?

Badging System: UNIX.COM Bug Hunter Badge (New)

I have moved the bug badge out of reserve and into the main stream. Basically, I will assign a color level like the others, based on who has made a good actionable bug report for UNIX.COM. "Good" means screenshots, links, and even details from web dev tools our the HTML source code. So far,... (0 Replies)
Discussion started by: Neo
0 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:00 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy