shm That Cache
I am often trying to find more space on my hard drives and found today my own docker containers wasting space thanks to ! Here's how I fixed it.
I am often trying to find more space on my hard drives and found today my own docker containers wasting space thanks to ! Here's how I fixed it.
Upon recently trying Deezer again, I found their web app ate all my memory when running in Firefox, so I decided to see if I could find out why. I got as far as memory-file-data/string and Blobs. Here's how.
In a culmination of litter surveys and litter picks, linked data and data exploration, and remoteStorage and ActivityPub, I have created a web-based litter pick/survey app that I hope will allow federated citizen science.
My latest litter pick target was Hoe Stream and the White Rose Lane Local Nature Reserve. Here's how it went.
I just created a Gitlab CI job to create a release with information from a CHANGELOG.md file for some of my projects. Here's how I did it.
I noticed something strange happening during build process during a multi-tasking bug fix. Turns out I was using Gitlab CI's caching incorrectly. I should have been using artifacts. Here's what I saw.
As a birthday treat, I took the day off work to try out my electronerised litter picker. Here's how it went.
In preparation for a day of litter picking, I finally got round to a project idea - attaching a camera to a litter picker to record it all. Here's what I did.
I finally started implementing UI testing on first-draft using WebdriverIO. While writing tests was easy, getting the tests running was a little more difficult. Here is how I did it.
Hooray! My new blog is live! Based on Sapper, using MongoDB and eventually ActivityPub and ActivityStreams, it will be my federated posting hub to the world.
Creating this new blog, I wanted to make sure there was no metadata data leaking personal information. Here's how I removed all the metadata tags except the ones I wanted from my photos.
Using tmux
for your terminal multiplexer but want an easy to reattach to a session? Here's a small bash script to do it.
Here's how to help your readers save time by making your post's shell commands easy to select and copy - with a simple CSS property.
Making my new blog, I didn't initially set the published dates to be native dates in the database. Here what I did to change them ...and do all the upgrades I needed.
I recently needed to test that some Vue components were creating the correct HTML. To do this, I decided to create snapshots of Object representations of the rendered HTML.
HTML5 number inputs aren't useful, but tel inputs, have all the power
I decided to look into the extortion emails I have been getting and wrote a small script to extract the bitcoin addresses that have been used.
As part of my pledge not to upgrade, I decided to repair two of my failing mice instead of replacing them with a brand new model (as tempting as it was). Here's what I did.
During a recent major merge event, we noticed that one of the pages of our C2 app was taking ages to load (140s is Chrome and explosions in Firefox) when you navigated back to it. The page is the page for monitoring science data coming off the platforms and contains plots and a map. Four of the plots are using scale-colored markers for representing different values, so the data for the graphs needs to be converted into colors before the data is passed to Plotly.js for rendering.
Upon looking at a performance snapshot of the page transition back to the science page, I saw that the function that generates that data for Plotly.js was taking 20 seconds to run each time it ran for each of the color graphs. With other issues we are having, this ballooned up to the enormous 140s load time. This wasn't the case when the page was initially loaded - the function only took 200ms to run through exactly the same data.
A little bit more zooming in on the performance snapshop and I saw that the issue was the Vue reactive variable functions that took around 60ms for each value accessed. These functions are set as the Getters and Setters for reactive data and are called whenever a value from a reactive Object is accessed and with 30000 values to access for each graph, these were causing major delays.
The difference in the initial load and going back to the page was that during the initial load, the data value was set outside of the component itself, which meant it avoided being turned into a reactive pumpkin. Whereas, when going back to the page, the data value was returned by a call to get the cached data and was then stored in the component by the component itself. As there was data watchers on the data and the data was used inside the component template, the component made the data value reactive.
I confirmed my suspicions by converting the data value to a normal object using a quick and dirty JSON.parse(JSON.stringify())
, which reduced the config function running time to a more acceptable 200ms. I then removed all references to it in the template, instead using a value that was set anytime the data value was changed using callbacks, and removed all functions watching the data value. Hey presto, problem solved.