Matt McKay

The results between `EC2` (left) and `GitHub Actions` (right) @jstac there is a really interesting mix of timing results here between the `V100` on EC2 and the `T4` on GitHub....

thanks @kp992 -- lots of changes here. Can you please fill in the top level comment box with a description of the change etc. (cc @jstac)

Just triggered a new `publish` so we are comparing like for like. (https://github.com/QuantEcon/lecture-jax/releases/tag/publish-2024may09)

@kp992 is this still in work?

> This is interesting @mmcky! Now since we are using GA's GPU for trial, shall we compare the costs that we were having through AWS and now on GA --...

@kp992 this is the `like-for-like` time comparisons now with the current `live` site. still an interesting mix of performance differences. **Machine Details:** **EC2:** Name | GPUs | vCPUs | RAM...

- [x] remove the docker container layer to see if that speeds up compute times

Currently the kernel is dying when installing directly onto the `vm` provided by github (rather than using our docker container). IT would be quicker and more efficient to get this...

> `{align*}` is an environment, which throws errors in latex, when its inside another environment like `$$` . Using `{aligned}` instead is the way to go. Thanks @AakashGfude 👍 --...

> Thanks @mmcky, are we moving forward with moving to Github Actions VM for all our repos using AWS? I would like to if we can -- as that is...