<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://labviewwiki.org/w/index.php?action=history&amp;feed=atom&amp;title=GDevCon-6%2FAvoiding_evening_coffee</id>
	<title>GDevCon-6/Avoiding evening coffee - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://labviewwiki.org/w/index.php?action=history&amp;feed=atom&amp;title=GDevCon-6%2FAvoiding_evening_coffee"/>
	<link rel="alternate" type="text/html" href="https://labviewwiki.org/w/index.php?title=GDevCon-6/Avoiding_evening_coffee&amp;action=history"/>
	<updated>2026-05-08T08:16:02Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.0</generator>
	<entry>
		<id>https://labviewwiki.org/w/index.php?title=GDevCon-6/Avoiding_evening_coffee&amp;diff=35895&amp;oldid=prev</id>
		<title>Cordm: Created page with &quot;{{infobox |category=presentation |icon=GDevConButton.png |presentation-conference=GDevCon-6{{!}}GDevCon#6 |presentation-presenter=Andrei Zagorodni }}  {{presentation |presenters=Andrei Zagorodni |abstract=Actually, the title is incomplete – let’s also avoid the morning coffee. Parallelization and no, not the kind you think. This isn’t about the parallel loops we build every day into LabVIEW programs. This is about short-lived, asynchronous runs even single VIs, no...&quot;</title>
		<link rel="alternate" type="text/html" href="https://labviewwiki.org/w/index.php?title=GDevCon-6/Avoiding_evening_coffee&amp;diff=35895&amp;oldid=prev"/>
		<updated>2026-02-05T13:25:50Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;{{infobox |category=presentation |icon=GDevConButton.png |presentation-conference=GDevCon-6{{!}}GDevCon#6 |presentation-presenter=Andrei Zagorodni }}  {{presentation |presenters=Andrei Zagorodni |abstract=Actually, the title is incomplete – let’s also avoid the morning coffee. Parallelization and no, not the kind you think. This isn’t about the parallel loops we build every day into LabVIEW programs. This is about short-lived, asynchronous runs even single VIs, no...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;{{infobox&lt;br /&gt;
|category=presentation&lt;br /&gt;
|icon=GDevConButton.png&lt;br /&gt;
|presentation-conference=GDevCon-6{{!}}GDevCon#6&lt;br /&gt;
|presentation-presenter=Andrei Zagorodni&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{presentation&lt;br /&gt;
|presenters=Andrei Zagorodni&lt;br /&gt;
|abstract=Actually, the title is incomplete – let’s also avoid the morning coffee.&lt;br /&gt;
Parallelization and no, not the kind you think. This isn’t about the parallel loops we build every day into LabVIEW programs. This is about short-lived, asynchronous runs even single VIs, no loops that still depend on each other and form complex patterns along time scale.&lt;br /&gt;
And they offer approaches that can save serious time for both developers and users.&lt;br /&gt;
&lt;br /&gt;
The clearest example? System initialization (and yes, deinitialization). Smart parallelization shortens startup and shutdown for the program and the hardware. Easy to implement in mid-sized, fixed configurations. But for large and reconfigurable systems? That’s where things get interesting.&lt;br /&gt;
So, this talk is about not needing a coffee break after clicking Start. And not thinking about coffee after clicking Stop.&lt;br /&gt;
For LabVIEW architects and seasoned developers who like their code fast and their mugs empty.&lt;br /&gt;
|youtube-id=KRMSscKcabw&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
[[Category:GDevCon-6]]&lt;/div&gt;</summary>
		<author><name>Cordm</name></author>
	</entry>
</feed>