Discussion
Loading...

#Tag

  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
d@nny disc@ mc虏 boosted
Ekaitz Zarraga 馃懝
@ekaitz_zarraga@mastodon.social  路  activity timestamp 2 weeks ago

I think I'm going live again because I'm having a very cool chat with people when I do. About programming, studies, interpreters... many things!

https://twitch.tv/ekaitzza

Also I have to say the issue that I have to track today is weird.

#GNU #Mes ( #scheme & #c #programming) bug hunting night.

Twitch

Twitch is the world's leading video platform and community for gamers.
  • Copy link
  • Flag this post
  • Block
Ekaitz Zarraga 馃懝
@ekaitz_zarraga@mastodon.social  路  activity timestamp 2 weeks ago

I think I'm going live again because I'm having a very cool chat with people when I do. About programming, studies, interpreters... many things!

https://twitch.tv/ekaitzza

Also I have to say the issue that I have to track today is weird.

#GNU #Mes ( #scheme & #c #programming) bug hunting night.

Twitch

Twitch is the world's leading video platform and community for gamers.
  • Copy link
  • Flag this post
  • Block
d@nny disc@ mc虏 boosted
Ekaitz Zarraga 馃懝
@ekaitz_zarraga@mastodon.social  路  activity timestamp last month

I think I managed to reduce GNU #Mes memory usage by quite a bit just being stubborn on understanding every single detail of the things I use.

3 lines of code for a max of 12% reduction on memory usage in a simple program execution.

It was hard to catch but easy to do, it was just the TBYTES memory layout had some size calculation error.

I think I did it right but I still need to test a little bit more.

Three graphs: the two on the top represent the same data and have the same shape. Those have two lines each, in orange: the memory usage before the change was implemented; in blue: the memory usage after the change was implemented. The one on the left is show in cells used, and the one on the right in MiB used.
The third graph (below) only shows one line that is the percentage of improvement. It goes from 2 to 12.
Three graphs: the two on the top represent the same data and have the same shape. Those have two lines each, in orange: the memory usage before the change was implemented; in blue: the memory usage after the change was implemented. The one on the left is show in cells used, and the one on the right in MiB used. The third graph (below) only shows one line that is the percentage of improvement. It goes from 2 to 12.
Three graphs: the two on the top represent the same data and have the same shape. Those have two lines each, in orange: the memory usage before the change was implemented; in blue: the memory usage after the change was implemented. The one on the left is show in cells used, and the one on the right in MiB used. The third graph (below) only shows one line that is the percentage of improvement. It goes from 2 to 12.
  • Copy link
  • Flag this post
  • Block
Ekaitz Zarraga 馃懝
@ekaitz_zarraga@mastodon.social  路  activity timestamp last month

I think I managed to reduce GNU #Mes memory usage by quite a bit just being stubborn on understanding every single detail of the things I use.

3 lines of code for a max of 12% reduction on memory usage in a simple program execution.

It was hard to catch but easy to do, it was just the TBYTES memory layout had some size calculation error.

I think I did it right but I still need to test a little bit more.

Three graphs: the two on the top represent the same data and have the same shape. Those have two lines each, in orange: the memory usage before the change was implemented; in blue: the memory usage after the change was implemented. The one on the left is show in cells used, and the one on the right in MiB used.
The third graph (below) only shows one line that is the percentage of improvement. It goes from 2 to 12.
Three graphs: the two on the top represent the same data and have the same shape. Those have two lines each, in orange: the memory usage before the change was implemented; in blue: the memory usage after the change was implemented. The one on the left is show in cells used, and the one on the right in MiB used. The third graph (below) only shows one line that is the percentage of improvement. It goes from 2 to 12.
Three graphs: the two on the top represent the same data and have the same shape. Those have two lines each, in orange: the memory usage before the change was implemented; in blue: the memory usage after the change was implemented. The one on the left is show in cells used, and the one on the right in MiB used. The third graph (below) only shows one line that is the percentage of improvement. It goes from 2 to 12.
  • Copy link
  • Flag this post
  • Block
Log in

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About 路 Code of conduct 路 Privacy 路 Users 路 Instances
Bonfire social 路 1.0.1-alpha.8 no JS en
Automatic federation enabled
  • Explore
  • About
  • Members
  • Code of Conduct
Home
Login