2
2
3
3
** Tapestry** is an experimental tensor expression optimizing compiler suite.
4
4
5
+ It exists to make it easy to optimize applications (such as AI) to maximally exploit both
6
+ datacenters full of GPUs, and integrated FPGA stacks.
7
+
5
8
See the [ Tapestry Documentation] ( docs/README.md ) for more information.
6
9
7
10
The goal of ** Tapestry** is to provide an ecosystem for a high-performance stochastic pareto-front
@@ -11,22 +14,53 @@ for extended time on a large number of machines.
11
14
Here are examples showing a ** Linear** /** ReLU** pipeline, with and without sub-block sharding;
12
15
demonstrating the potential for sub-shard operation fusion:
13
16
14
- <img alt =" linear.relu " src =" docs/media/linear.relu.ortho.jpg " width =" 800 " />
15
- <img alt =" linear.relu.4x " src =" docs/media/linear.relu.4x.ortho.jpg " width =" 800 " />
17
+ <table cellborder =" 0 " >
18
+ <tr >
19
+ <td>
20
+ <div style="width: 100%; margin: auto">
21
+ <img alt="linear.relu" src="docs/media/linear.relu.ortho.jpg"/>
22
+ </div>
23
+ </td>
24
+ <td>
25
+ <div style="width: 100%; margin: auto">
26
+ <img alt="linear.relu.4x" src="docs/media/linear.relu.4x.ortho.jpg"/>
27
+ </div>
28
+ </td>
29
+ </tr >
30
+ </table >
16
31
17
- ## Getting Started
32
+ ## Contributing
18
33
19
34
I'm actively looking for contributors to help with building or reviewing the project.
20
35
21
36
If you'd like to get involved, please post any questions in the project
22
37
[ Discussions] ( https://github.com/crutcher/loom/discussions ) board, or open an issue.
23
38
39
+ We could create a Discord server; if we got enough traction.
40
+
41
+ I'm particularly interested in contributors with experience in the following areas:
42
+
43
+ - maven lifecycle / package publishing
44
+ - technical documentation / editing
45
+ - compiler design
46
+ - tensor algebra
47
+ - optimization theory
48
+ - graph transformations
49
+ - graph representation
50
+ - distributed computing
51
+ - graph visualization
52
+
53
+ ## Getting Started
54
+
24
55
In the current stage of development, ** loom** produces no tool targets; and exists solely as a
25
56
collection of libraries and tests.
26
57
27
58
It ** should** setup cleanly in any modern development environment; but full external dependencies
28
59
are not yet documented.
29
60
61
+ Documenting missing dependencies is a high priority and setup instructions is another high priority
62
+ which contributors could help with.
63
+
30
64
## Active Work Surfaces
31
65
32
66
- [ Metakernel Template Language Design] ( https://github.com/crutcher/loom/issues/2 )
0 commit comments