Huge performance differences WRT tasks.json

I have been using a tasks.json file in VS Code to compile my app and it looks like this:

{
	"version": "0.1.0",
	"command": "asconfigc",
	"isShellCommand": true,
	"args": [
		"--sdk=/Apache/royale-asjs"
	],
	"showOutput": "always"
}

When I compile with "debug": false in my asconfig.json, I’m getting about a 36 second compile time in my app (about 10 seconds with "debug": true).

When I remove the tasks.json file and let VS Code compile using the internal version of asconfigc, I’m getting about 80 second compile times for release. This is using the exact same asconfig.json file. It’s interesting to note that the build times when running an ant script is similar to the build times when I don’t have a tasks.json file defined. This makes me wonder if running the compiler from Java somehow slows down builds.

[joshtynjala]

It’s certainly possible that starting up two instances of the JVM is slower. You could set nextgenas.asconfigc.useBundled to false, and it will use the Node version instead. This will probably perform similarly to your tasks.json.

If VSCode ever adds the ability to run a “command” as a task, I’ll be able to run asconfigc from the already running language server. It shouldn’t require starting Node or Java, so it should be faster than both.

[joshtynjala]

@Harbs I just discovered that you can customize the terminal.integrated.scrollback setting in VSCode to keep a longer terminal history.