pprofit | utilities written in Go for working with the profiling | Monitoring library
kandi X-RAY | pprofit Summary
kandi X-RAY | pprofit Summary
The Golang profiling tools are a pain to get set up in Windows, and they’re quite dated compared to the tools available in IDEs like Visual Studio nowadays. The over-ambitious goal of this is to start building a cross platform toolkit for the profiling of the performance of Go programs using Go itself and web browsers as the IDE. Being able to recreate the results from would be expecially nice. The largest problem may end up being that there is currently no debugging information available on the Windows platform. Until that issue is resolved somehow, a lot of the most detailed information in the blog may be unavailable on Windows, but we can still make the tools that are available more accessible.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- profileHeadersFromReader reads profile headers from r .
- processSymbolResponse processes a symbol response .
- Fetch is the profiler interface
- ReadProfile reads a profile from a io . Reader .
- GetFunctionNames fetches a list of symbol names .
- HttpProfileServer runs the http profile server .
- readSample reads a sample from a reader .
- init initializes cli . Command .
- CreateProfile creates a CPU profile .
- WriteProfileToDisk writes profile to disk .
pprofit Key Features
pprofit Examples and Code Snippets
Community Discussions
Trending Discussions on pprofit
QUESTION
I use different kinds of stop losses and would like to be notified (SendNotification()
) about which kind of stop loss was hit upon trade exit.
Let's say I entered a trade by...
...ANSWER
Answered 2018-May-11 at 12:54There was never a way to do this in MQL4/5 trading platformsI would now like to have the
request.comment
changed
Sad, but true.
The core-functionality was always focused on engineering a fast, reliable soft-real-time ( providing still just a best-effort scheduling alongside the stream of externally injected FxMarket-Event-Flow ), so bear with the product as-is.
Plus, there was always one more degree-of-uncertainty, the Broker-side automation was almost free for modifying the .comment
-part of the Trade-position, so even if your OrderSend()
was explicit on what ought be stored there, the result was unsure and the Broker-side could ( whenever, be it immediately or at any later stage ) change this field outside of any control ( which was not left on your side ), so the only semi-UUID# keys could have been placed into the .magic
( and your local-side application code always had to do all the job via some key:value
storage extension to the otherwise uncertain Broker-side content.
Even the Trade number ( ID, ticket
) identifier is not always a persistent key and may change under some Trade management operations, so be indeed very carefull, before deciding your way.
Doable, yet one will need to build all the middleware-logic on one's own :like to be notified (
SendNotification()
) about which kind of stop loss was hit upon trade exit.
The wish is clear and doable. Given a proper layer of middleware-logic will get built, one can enjoy whatever such automation.
Having built things like an augmented-visual-trading, remote AI/ML-quant-predictors or real-time fully-adaptive non-blocking GUI-quant-tools augmentations ( your trader gets online graphical visual aids inside GUI, automatically overlaid over other EA + Indicator tools on the GUI-surface, fully click-and-modify interactive / adaptive for fast visually augmented discretionary modifications of the traded asset management ), so only one's imagination and resources available are one's limit here.
Yet, one has to respect the published platform limits - the same as OrderModify()
does not provide any means for the wish above, the add-on traded assets customer-specific reporting on position terminations is to be assembled by one's own initiative, as the platform does not provide ( for obvious reasons noted above ) any tools, relevant for such non-core activity.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install pprofit
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page