TaskGraph or TaskSchedule?

[zealbell]

In my maven project (since I am trying to replicate some examples from the TornadoVM repo), I have the following dependencies added tornado-api and tornado-matrices versions 0.14.1 but I’m getting IDE errors about import uk.ac.manchester.tornado.api.TaskGraph

I took a look at the tornado-api-0.14.1.jar from my project, lo and behold TaskGraph was nowhere to be found in it. I compared contents of the jar with TornadoVM/tornado-api and then I spotted a lookalike instead: “TaskSchedule”.

I tried to make things work by simply swapping names in my project… currently everything is falling apart. Please Help🙏🏾

[jjfumero]

The TaskGraph is new only if you get the latest version from the master or develop branch. It is still work-in-progress. If you are using the official release (e.g., 0.14.1, you won't see the TaskGraph yet. You simply use the TaskSchedule and the calls associated with it.
We highly recommend checking the examples package of TornadoVM to get an idea about how the APIs are called.

Having said this, we are working on a new release, hopefully by the beginning 2023, with TaskGraph and a set of new interfaces. Just to be aware of this. We will also release a document that explains the migration of existing code to the new APIs and new documentation about the new APIs.

[zealbell]

Hi, Just got back on my feet (I fell sick). I only wish to run (or use) tornado (api) from my standalone maven project (not via the cloned master branch), currently this is what I get:

/home/linker/TornadoVM/etc/dependencies/TornadoVM-GraalJDK17/graalvm-ce-java17-22.2.0/bin/java -server -XX:-UseCompressedOops -XX:+UnlockExperimentalVMOptions -XX:+EnableJVMCI -Djava.library.path=/home/linker/TornadoVM/bin/sdk/lib  --module-path .:/home/linker/TornadoVM/bin/sdk/share/java/tornado -Dtornado.load.api.implementation=uk.ac.manchester.tornado.runtime.tasks.TornadoTaskGraph -Dtornado.load.runtime.implementation=uk.ac.manchester.tornado.runtime.TornadoCoreRuntime -Dtornado.load.tornado.implementation=uk.ac.manchester.tornado.runtime.common.Tornado -Dtornado.load.device.implementation.opencl=uk.ac.manchester.tornado.drivers.opencl.runtime.OCLDeviceFactory -Dtornado.load.device.implementation.ptx=uk.ac.manchester.tornado.drivers.ptx.runtime.PTXDeviceFactory -Dtornado.load.device.implementation.spirv=uk.ac.manchester.tornado.drivers.spirv.runtime.SPIRVDeviceFactory -Dtornado.load.annotation.implementation=uk.ac.manchester.tornado.annotation.ASMClassVisitor -Dtornado.load.annotation.parallel=uk.ac.manchester.tornado.api.annotations.Parallel  -XX:+UseParallelGC  @/home/linker/TornadoVM/bin/sdk/etc/exportLists/common-exports @/home/linker/TornadoVM/bin/sdk/etc/exportLists/ptx-exports --add-modules ALL-SYSTEM,tornado.runtime,tornado.annotation,tornado.drivers.common,tornado.drivers.ptx 

What flags are not correctly set?

I did this earlier ($tornado --printJavaFlags) and you said my flags were ok

[jjfumero]

As flags in the IDE you can't use the /home/linker/TornadoVM/etc/dependencies/TornadoVM-GraalJDK17/graalvm-ce-java17-22.2.0/bin/java. THis is not a Java flag, This is the path to your Java installation.

[zealbell]

I am not sure I quite follow with your last message. Are you hinting that after I run the $ tornado --printJavaFlags command, I have to manually set my IDE flags to be exactly as the output I get?

[jjfumero]

You need to configure your IDE to launch your applications using the Java flags displayed from the command: tornado --printJavaFlags without the path to Java (obviously).

Can you share how are you running your Java programs in your editor? Which IDE are you using?

Otherwise, you can use the command line to run your TornadoVM programs.

[zealbell]

I am using Intellij, I am running my project by building with maven. I thought the tornado --printJavaFlags output were flags currently set automatically by the IDE in sync with the maven build.

[zealbell]

Hi Juan, Big Thanks🔥. My card is spinning⚡️ currently, I went over everything you said again, everything now works. I am just back to post about my journey so far on this thread to help others because I feel most of the issues I encountered could have been avoided if there was some blog or guide about creating a standalone tornado maven project in Intellij.

INSTALLATION

$ cd /home/linker
$ git clone https://github.com/beehive-lab/TornadoVM.git
$ cd TornadoVM
$ ./scripts/tornadoVMInstaller.sh --graal-jdk-17 --opencl --ptx

SETUP

• Intellij: creation of 'Tornadoes' as a maven project (i.e. /home/linker/Tornadoes | current version in my pom.xml is 0.15-dev instead) with MatrixMultiplication2D.java example from the TornadoVM master branch.

LAUNCH

• Open the project TornadoVM

BUILD (ONETIME/SETUP) [ previously: BUILD (EVERYTIME/LAUNCH) ]

$ cd /home/linker/TornadoVM
$ . source.sh
$ make graal-jdk-11-plus BACKEND=ptx 

CONFIGURATION (ONETIME/PROGRAM)

$ tornado --printJavaFlags

• Intellij --> Run --> Edit Configurations --> <Your Program> --> Modify Options --> Add VM Options >> VM Options | paste $ tornado --printJavaFlags output without the java path (i.e. starting from -server...) --> Apply --> Ok

TESTING
my ❤️ly output:

Computing MxM of 512x512
Single Threaded CPU Execution: 1.18 GFlops, Total time = 227 ms
TornadoVM Execution on GPU (Accelerated): 268.44 GFlops, Total Time = 1 ms #didn't think tornado would be this fast... nice!
Speedup: 227.0x
Verification true

after running /home/linker/Tornadoes/src/main/java/org/example/MatrixMultiplication2D.java

[jjfumero]

To clarify, you do not need to build TornadoVM every time, but there are a few exceptions:

1. You modify the TornadoVM project.
2. You want to access another backend (e.g., SPIR-V). In this case, you recompile TornadoVM with the desired backends.

Otherwise, it just needs to build once, as with any other Java project.

[zealbell]

Oh! alright then. thankie😊