From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: [FFmpeg-devel] AVDictionary vs. AVSet (AVDictionary2 approximation) Date: Mon, 14 Apr 2025 13:33:28 +0200 Message-ID: <20250414113328.GM4991@pb2> (raw) [-- Attachment #1.1: Type: text/plain, Size: 2709 bytes --] Hi I just posted a AVSet implementation i wrote in the last 2 days (yes thats why i did dissapear for the last 2 days) My plan was to use that AVSet as basis for AVDictionary2 in case benchmarks indicate that its worth it, so is it ? with 3 entries (100000 runs) AVDictionary 0.040sec AVSet 0.027sec with 5 entries (100000 runs) AVDictionary 0.065sec AVSet 0.042sec with 10 entries (100000 runs) AVDictionary 0.193sec AVSet 0.087sec with 100 entries (100000 runs) AVDictionary 8.7 sec AVSet 1.4 sec with 1000 entries (1000 runs) AVDictionary 8.0 sec AVSet 0.240 sec with 10000 entries (10 runs) AVDictionary 7.2 sec AVSet 0.042 sec I was a bit surprised for the 3 and 5 entry case, maybe my benchmark is buggy or AVSet is, but then AVDictionary is pretty bad with memory allocations AVDictionary needs to strdup every key and value, needs to allocate the AVDictionary itself and reallocs the entry array each time thats 10 memory allocation related calls for adding 3 entries while AVSet allocates the AVSet and then uses av_fast_realloc() for the array and theres nothing else, the key/value goes in that array too bechmark code used is below: #if 0 for (int runs = 0; runs < 100000; runs++) { AVSet *set = av_set_new(strcmp, NULL, NULL); for(int pass = 0; pass < 2; pass++) { unsigned r = 5; for(int i=0; i<100; i++) { r = r*123 + 7; char str[2*7] = "TESTXXTESTXX"; str[4] = r; str[5] = r>>8; if(pass == 0) { av_set_add(set, str, 2*7, 0); } else { av_set_get(set, NULL, str, NULL); } } } av_set_free(&set); } #else for (int runs = 0; runs < 100000; runs++) { AVDictionary *dict = NULL; for(int pass = 0; pass < 2; pass++) { unsigned r = 5; for(int i=0; i<100; i++) { r = r*123 + 7; char str[7] = "TEST"; str[4] = r; str[5] = r>>8; if(pass == 0) { av_dict_set(&dict, str, str, 0); } else { av_dict_get(dict, str, NULL, 0); } } } av_dict_free(&dict); } #endif -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws. -- Plato [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next reply other threads:[~2025-04-14 11:33 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-04-14 11:33 Michael Niedermayer [this message] 2025-04-14 12:40 ` softworkz . 2025-04-14 13:02 ` softworkz . 2025-04-15 19:11 ` Michael Niedermayer 2025-04-15 20:36 ` Michael Niedermayer
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20250414113328.GM4991@pb2 \ --to=michael@niedermayer.cc \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git