Estimer le Temps D'exécution

J'ai créé dernièrement un petit utilitaire en Java qui peut exécuter une commande (donc un programme) et calculer le temps d'exécution. le retard de l'application est, dans le pire des cas, de 3 milli-secondes, donc négligeable dans le cas des exécutions excédant une seule seconde.
Le problème avec ces milli-secondes est que Java est un langage de haut niveau, et on y ajoute une machine virtuelle qui ralentit le traitement. De plus, je teste cet utilitaire sous Gnome, le bureau lourd de Linux. et ajoutant à ça l'exécution simultanée de NetBeans, alors c'est justifiable de perdre ce 1/1000 de secondes.

Ci-joint des images du programme, code source sous NetBeans et mon répertoire bin/ dans mon dossier personnel (je met l'archive exécutable JAR là-bas et j'appelle de la ligne de commande. c'est tout!)
J'ai amélioré le code de plusieurs façons durant son écriture. Je crois qu'un tel utilitaire est utile, mais beaucoup de logiciels plus efficaces existent. Pour ceux qui développent sur NetBeans, l'ajout du module "Profiler" donne un outil indispensable pour surveiller le temps et les performances de votre application.

Commentaires

Posts les plus consultés de ce blog

GNS3: Simulating a 100% opensource site2site VPN using Wireguard, VyOS and OpenVSwitch

This is something I had in mind but didn't find the time to accomplish before. It just took a very cold day to convince me that I have to play with Wireguard on VyOS. I used GNS3 of course, on my personal Linux laptop to create this setup. Of course the performance was not that great since it is just a simulation. In real life, I am using Wireguard on a 10 years old Raspberry Pi Model B and amazingly with just a 700MHz single core ARM CPU and less than 512 MB of RAM I had a decent and stable permanent Wireguard tunnel. (My bandwidth would reach 24 Mbps without issue) Back to my simulation, this is what it looks like : Quick explanation: the VYOS routers labeled IPERF1 and IPERF2 are only used for an iperf3 test, which was able to reach about 50 to 60 Mbps each time. It ain't much but it was honest (and free) secure bandwidth! I won't get into the details of this setup but I will just post the two most important configurations : R-East and R-West : #### VYOS WireGuard Site...

GNS3 on Manjaro/Arch Linux: How to create virbr0 for NAT to work

Problem: You can't add a NAT connection to your GNS3 simulation, and you get the error : "ERROR template_manager:226 Error while creating node from template: NAT interface virbr0 is missing, please install libvirt" Steps to resolve: 1- Create a file named /tmp/default.xml 2- Paste this content and save: <network> <name>default</name> <bridge name="virbr0"/> <forward mode="nat"/> <ip address="192.168.123.1" netmask="255.255.255.0"> <dhcp> <range start="192.168.123.2" end="192.168.123.254"/> </dhcp> </ip> </network> 3- Execute the following commands in your shell : virsh net-define /tmp/default.xml sudo virsh net-start default sudo virsh net-autostart default

AutoWG: a simple Bash script to connect two devices with Wireguard

I made today a quite simple BASH script that allows to connect two devices running Wireguard (tested with Debian Linux 12, but should work with any device) You can check it out (and fork it if you want) in this Gitlab Page This is the source code as of now, but I could modify it later (any suggestions are welcome) : #!/bin/bash # # AUTOWG written by Hamdi KADRI # No copyright in any form or kind # This script is intended to create configurations for # a point-to-point Wireguard connection between a server # and a client (/30 network) # # Step zero: declare configurations as variables servercfg="[Interface] Address = <serverwgIP> SaveConfig = true ListenPort = <port> PrivateKey = <server-privatekey> [Peer] PublicKey = <client-pubkey> AllowedIPs = <clientwgIP> " clientcfg="[Interface] PrivateKey = <client-privatekey> Address = <clientwgIP> [Peer] PublicKey = <server-pubkey> AllowedIPs = 0.0.0.0/0 EndPoint = <serverIP...

HK blog

Rechercher dans ce blog