Introducing the APM Meter for Desktop

Hi all,

First post here, this blog intends to be my code snippet / software first dumping ground
For the first software, feel free to download APM Meter:

 Brief description of what is APM (from wikipedia):
Actions Per Minute, commonly abbreviated as APM, is a term used in the real time strategy field of cybersport which refers to the total number of actions that a player can perform in a minute.
http://en.wikipedia.org/wiki/Actions_per_minute


An Example of High APM person:


Well, initially I created this little piece of software just for fun and out of frustration of not being able to find any APM Meter for desktop, I was thinking that it would be cool if we can record the APM of our work desktop, during work hours, to see how fast and how efficient we are at doing our task in the office. Then I start having ideas on how to remove / block APM counts of chats, facebook and the like. Eventually the APM meter becomes more than just a simple keypress and mouse click counting software.

Anyway here is the download link to the APM Meter, enjoyy!!
http://www.mediafire.com/?1w5naqdp76jktuw

RAR file password: abc123
SHA512 of the RAR file: 583d4e63cb8911a06fcdb32e58658a4756d468918d7ebf93050ff19fe254c98d33f80ed01130f2874be51466d81c0a60b264bc1c128dc65f2ee668b5cae85140

SHA512 of the EXE file: 4fae3bfba590f11c6a43aa0ff08825de13f9f1c50a79e55c0890b467ea5c8a0c5b7b80a75a55a47ea45449ffed99a3a83a02a5b944dc686b9810ec88654ad04a

Comments

Post a Comment

Popular posts from this blog

Image
Implementing gRPC Using Spring Boot and Gradle Background GRPC (gRPC) is a RPC framework pioneered by google later on made public and open source. GRPC has not been officially supported by Spring Framework, so far there are few community libraries that can work seamlessly with Spring Boot. In this article, I will use the lognet's grpc-spring-boot-starter. Project Structure Ideally, the proto files for gRPC is located in another directory, which will then be accessed by the gradle plugin to auto generate the required files.   Gradle Script The heart of gRPC enablement lies on the grpc boot starter, which includes few other tasks outlined as below. https://github.com/overtakerx/grpcbootdemo/blob/main/build.gradle Few important note: first you have to run gradlew compileJava for the auto generation to generate the files from the proto file, then you will need to rebuild the project for Intellij to recognise the auto-generated files. Full demo: https://github.com/overtakerx/grpcbootdem
Read more

Spring Boot 2: Parallelism with Spring WebFlux

Image
Spring Boot 2: Parallelism with Spring WebFlux Parallelism is rather unusual in Spring application, however when we encounter the need of HITLOL (HIgh Throughput LOw Latency), we need ways to make async calls. With Spring Boot 1, in high level definition, we can declare async on all the functions that are meant to be parallel and return Futures from there. Here is more detailed info:  https://medium.com/sipios/how-to-make-parallel-calls-in-java-springboot-application-and-how-to-test-them-dcc27318a0cf For Spring Boot 2, we shall employ Spring WebFlux libraries to accomplish parallelism. Mainly focused on functions: Mono.zipDelayError(), Mono.subscribeOn() and Mono.onErrorResume() The main function that drives the parallelism is zipDelayError(), the purpose of zipDelayError() as supposed to using zip() is to enable the other Monos to run to completion even if one Mono failed. AllDtos allDtos = Mono. zipDelayError (Arrays. asList (firstDto , secondDto , (Mono&l
Read more

Spring Boot Reactive API Part 2

Image
 Spring Boot Reactive: Improving CPU bound performance using Scheduler In part 1 , we have seen that Spring Boot Reactive doesn't really improve performance if the WAITING time is CPU bound / CPU intensive tasks. This article show a quick way on how we can improve the speed through specific configuration Setup Spring Boot's embedded Tomcat is reconfigured to only use 10 worker threads, this way we can clearly see the performance limitation and tweaks. Gatling is configured to simulate 30 concurrent requests with 30000 milliseconds request timeout. APIs internal process is calling java native code that calculate the value of PI over 1 million iterations Default / No scheduler The main reason why CPU bound tasks do not improve (or even degrade) with high parallelism is because of the costly overhead for context switching in the low level. In the scenario below, 10 main threads are all being used to calculate PI values and because there are less CPU than threads, a lot of context
Read more