# AutoSysimages.jl - Automate user-specific system images

**URL:** https://discourse.julialang.org/t/autosysimages-jl-automate-user-specific-system-images/87359
**Category:** Package Announcements
**Tags:** sysimage
**Created:** [September 16, 2022, 10:49am UTC](https://discourse.julialang.org/t/autosysimages-jl-automate-user-specific-system-images/87359 "2022-09-16T10:49:50Z")
**Posts on this page:** 7
**Page:** 2

<div class="post-metadata">

### Author: ![joa-quim](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/joa-quim/32/227_2.png) [@joa-quim](https://discourse.julialang.org/u/joa-quim)
#### Post date: [September 17, 2022, 2:14pm UTC](https://discourse.julialang.org/t/autosysimages-jl-automate-user-specific-system-images/87359/21 "2022-09-17T14:14:01Z")

</div>

Thanks, but a bit cryptic the description of the `packages_to_include()` function.

---

<div class="post-metadata">

### Author: ![ufechner7](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ufechner7/32/51363_2.png) [@ufechner7](https://discourse.julialang.org/u/ufechner7)
#### Post date: [September 17, 2022, 9:40pm UTC](https://discourse.julialang.org/t/autosysimages-jl-automate-user-specific-system-images/87359/22 "2022-09-17T21:40:05Z")

</div>

This issue disappeared, I assume because I added the package Plots to my project file, see latest version of [GitHub - ufechner7/Plotting](https://github.com/ufechner7/Plotting).

But the speed gain is still not as high as expected:

```julia
asysimg> @time include("src/plot.jl")
To zoom, draw a rectangle while keeping the right mouse key pressed!
To go back to see the full graph, press <CRTRL><f>
 11.709348 seconds (28.54 M allocations: 1.523 GiB, 4.72% gc time, 78.63% compilation time: 3% of which was recompilation)

```

compared to

```julia
julia> @time include("src/plot.jl")
To zoom, draw a rectangle while keeping the right mouse key pressed!
To go back to see the full graph, press <CRTRL><f>
 15.501547 seconds (38.28 M allocations: 2.051 GiB, 4.30% gc time, 78.86% compilation time: 12% of which was recompilation)

```

---

<div class="post-metadata">

### Author: ![petvana](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/petvana/32/20881_2.png) [@petvana](https://discourse.julialang.org/u/petvana)
#### Post date: [September 21, 2022, 11:59am UTC](https://discourse.julialang.org/t/autosysimages-jl-automate-user-specific-system-images/87359/23 "2022-09-21T11:59:23Z")

</div>

**Update**

It seems that all the problems reported by @ufechner7 are already fixed.

Moreover, we have simplified the installation process to

```julia
using AutoSysimages
install()

```

---

<div class="post-metadata">

### Author: ![juliohm](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/juliohm/32/215266_2.png) [@juliohm](https://discourse.julialang.org/u/juliohm)
#### Post date: [September 21, 2022, 12:08pm UTC](https://discourse.julialang.org/t/autosysimages-jl-automate-user-specific-system-images/87359/24 "2022-09-21T12:08:38Z")

</div>

@petvana I wonder if we could have a workflow that doesn’t require creating an external symbolic link to Julia. Maybe the package could run a new Julia process with the desired options in order to activate the autosysmage mode? Something like:

```julia
using Autosysimages

autosysimg() # launchs a new Julia process with the necessary options

```

---

<div class="post-metadata">

### Author: ![petvana](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/petvana/32/20881_2.png) [@petvana](https://discourse.julialang.org/u/petvana)
#### Post date: [September 21, 2022, 12:18pm UTC](https://discourse.julialang.org/t/autosysimages-jl-automate-user-specific-system-images/87359/25 "2022-09-21T12:18:04Z")

</div>

@juliohm In general, it seems possible to support both alternatives. However, your alternative would load the whole package which takes some time, as reported in [Startup and shutdown overhead · Issue #20 · petvana/AutoSysimages.jl · GitHub](https://github.com/petvana/AutoSysimages.jl/issues/20)

---

<div class="post-metadata">

### Author: ![louisponet](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/louisponet/32/2070_2.png) [@louisponet](https://discourse.julialang.org/u/louisponet)
#### Post date: [September 23, 2022, 9:02am UTC](https://discourse.julialang.org/t/autosysimages-jl-automate-user-specific-system-images/87359/26 "2022-09-23T09:02:00Z")

</div>

Is it possible to still use one’s own startup file? It seems mine is not picked up

---

<div class="post-metadata">

### Author: ![petvana](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/petvana/32/20881_2.png) [@petvana](https://discourse.julialang.org/u/petvana)
#### Post date: [September 23, 2022, 2:27pm UTC](https://discourse.julialang.org/t/autosysimages-jl-automate-user-specific-system-images/87359/27 "2022-09-23T14:27:02Z")

</div>

@louisponet Yes, it runs startup file, if exits. At the end, it’s just a normal julia called with two extra arguments

```bash
julia -J sysimage -L start.jl [USER-ARGS]

```

where `start.jl` script initializes the package by calling

```julia
import AutoSysimages
AutoSysimages.start()

```

The `asysimg` script only select the proper arguments for your specific project.

**Edit:** Actually, the startup file has been loaded twice by a mistake, so I’ve fixed that in [PR #26](https://github.com/petvana/AutoSysimages.jl/pull/26).

[Previous page](https://discourse.julialang.org/t/autosysimages-jl-automate-user-specific-system-images/87359.md?page=1)