-
Notifications
You must be signed in to change notification settings - Fork 12.2k
ggml : implement op fusion, starting with REGLU/GEGLU/SWIGLU #14158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I missed that these ops change the shape of the input tensor.
I think it would be better to introduce:
enum ggml_glu_op {
GGML_GLU_OP_REGLU,
GGML_GLU_OP_GEGLU,
GGML_GLU_OP_SWIGLU,
};
// similar to ggml_unary()
GGML_API struct ggml_tensor * ggml_glu(
struct ggml_context * ctx,
struct ggml_tensor * a,
enum ggml_glu_op op);
// these simply call ggml_glu()
GGML_API struct ggml_tensor * ggml_reglu(
struct ggml_context * ctx,
struct ggml_tensor * a);
GGML_API struct ggml_tensor * ggml_geglu(
struct ggml_context * ctx,
struct ggml_tensor * a);
GGML_API struct ggml_tensor * ggml_swiglu(
struct ggml_context * ctx,
struct ggml_tensor * a);
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hope we don't forget to implement these in the rest of the backends.
Adding @JohannesGaessler for review of the CUDA changes.
Yes, let's add the rest of the backends first before merging. At least Metal and Vulkan. |
More generally, I've been thinking that it would be useful to have something like a backend-specific graph optimization step in ggml. That way you could do things like fuse tensors only if the fused tensor is supported by the backend and only if using it makes sense given the tensor shapes. |
Any suggestions on who could help with that? |
struct ggml_context * ctx, | ||
struct ggml_tensor * a); | ||
|
||
GGML_API struct ggml_tensor * ggml_swiglu( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just want to note that I have been observing one variants of swiglu. it's used by ultravox, which sigmoid the second half of the vector instead of the first half
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, interesting, worth adding a parameter for, or best just handling in conversion?
https://huggingface.co/fixie-ai/ultravox-v0_5-llama-3_3-70b/blob/main/ultravox_model.py#L701-L704
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be nice to have a param since the GGUFs are already on the internet. Haven't thought about permuting the FFN up tensor before, nice suggestion
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added swapped variants.
@ggerganov I didn't dare update metal code, so needs to be implemented there too. :)
@0cc4m @jeffbolznv are either of you interested in a Vulkan implementation? |
I can look into it tomorrow. |
CUDA performance test:
Also a plot of the same data using #14169 : |
Huh, I didn't expect the benefit to be that much. Interesting. |
Everything other than mat-mat mul is either bandwidth or small dispatch limited. Fusion is a big opportunity. We should reopen discussions about how to enable more types of fusion. |
Nice! Will be interesting to see numbers on other backends as well... |
Hmmm, it just occurred to me that we should be able to (now that I pass along a pointer to the gate separately) perform these ops on models with separate ffn_up/gate tensors too by conditionally setting src[1]. |
struct ggml_context * ctx, | ||
struct ggml_tensor * a); | ||
|
||
GGML_API struct ggml_tensor * ggml_geglu( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tbh I don't even know why geglu was added in the first place. It doesn't seem to be used by any models. And to make matter worse, the PR where it was added has no useful description: #14074
So I wonder if we actually need to implement it as a kernel. The current kernel use tanh approximation, but in practice, there can be many different approximations for gelu op.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've seen several, and in fact we already support a few (Gemma, DeepSeekV1, Jina-Bert and T5), it's just that the gate is split (some at conversion because we didn't have the op).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So I wonder if we actually need to implement it as a kernel. The current kernel use tanh approximation, but in practice, there can be many different approximations for gelu op.
It's pretty easy adding different GLU ops (and in CUDA I even reuse the original op), adding GEGLU_ERF if necessary shouldn't be a problem.
I implemented Vulkan shaders for the new ops. |
Interesting.. I tried implementing for SYCL, saw little improvement. When I saw the graph logs, it wasn't using the fused kernels for llama 3.2 3B.
I am using from this branch. |
Hi. I plan to rebase this branch with master today but I am seeing conflicts in metal backend code as well. I'll try my best but if something goes incorrect please do correct it in the next commit. Thank you. |
ggml-ci
ggml-ci
* implement GLU for split up/gate * add tests for ggml_glu_split * Vulkan: Implement glu_split logic and shader support * add split to logging [no ci] * SYCL: refactor element_size ops and add split up and gate support to gated kernels * SYCL: switch GEGLU to use tanh approximation --------- Co-authored-by: 0cc4m <picard12@live.de> Co-authored-by: Akarshan <akarshan@menlo.ai>
c2af58b
to
a234e09
Compare
Thanks. :) |
…nlining This commit refactors the SYCL element-wise operations to improve performance by: - Inlining unary operations (sgn, abs, elu, gelu, silu, etc.) to reduce kernel launch overhead. - Introducing helper functions `op_xxx` for each unary operation to encapsulate the logic. - Replacing direct kernel calls with calls to these inlined functions. - Using `__dpct_inline__` to encourage compiler inlining. - Minor code cleanup and consistency improvements. The changes aim to reduce kernel launch overhead and improve the overall efficiency of element-wise operations on SYCL devices.
@qnixsynapse The latest improvements are probably worth extracting into a separate PR instead of keeping them locked away here. |
This one's the last, to partially address one of the review comments here. |
I did a quick proof of concept of how to detect fusion opportunities in jeffbolznv@2ed9fb4. This adds the use_count, reverts the llama-graph changes in this PR, and implements a peephole optimization that converts the views+conts+mul+silu into swiglu. I verified it successfully fuses and has the same perf as this PR. When it fuses, it's modifying the node->op to the new GGML_OP_SWIGLU added in this change, and changing the other tensors to GGML_OP_NONE. I haven't thought through what's the best way to represent fused operations in the backend. Maybe it's GGML_OP_FUSED, or maybe not, but there may be additional storage needed to save certain information about the combined operation, if we don't want to regenerate it multiple times. Given how complete the implementation of GGML_OP_GLU is, IMO we should go ahead with this PR as-is and not block it waiting on fusion support. This pattern is a bit trickier than the usual sequence of elementwise operations and isn't something I'd expect to cover in the initial implementation of fusion. |
Sweet, though I guess it gets a little more complicated for a proper implementation as this is (for PoC simplicity) done after graph split and does not take backend support into consideration. Very cool though! |
I wonder if it would be possible to make a parallel graph node that bridges the ops that can be fused with the fused op so that it can be an optional route while still keeping the unfused route. Edit: This means you can have smaller fusions as well, if backends don't support a larger fusion op. |
I am not sure that doing the operation fusing in What I was thinking about would be adding a function to check if operator fusion is possible that the backends can use to easily determine if they can fuse a sequence of operations. Roughly, something like this: ggml_status graph_compute(ggml_backend_t backend, struct ggml_cgraph * cgraph) {
for (int node = 0; node < cgraph->n_nodes; node++) {
if (ggml_can_fuse(cgraph, node, { GGML_OP_MUL_MAT, GGML_OP_ADD, GGML_OP_UNARY }, 3)) {
compute_fused_mul_mat_bias(...);
node += 2;
} else if (ggml_can_fuse(cgraph, node, { GGML_OP_MUL_MAT, GGML_OP_ADD }, 2)) {
compute_fused_mul_mat_bias_act(...);
node += 1;
} else {
// run unfused operation
compute_node(...);
}
}
return GGML_STATUS_SUCCESS;
} This would not really work for something like SWIGLU, but I think that's complex enough that it deserves to have it own operation. |
Sure, I'm happy to do it that way. I mostly wanted to show what the peephole detection looks like, for a complex case like this. |
Implement REGLU/GEGLU/SWIGLU ops to avoid unnecessary tensor duplications and a little more efficient execution by combining ops in one.Implement op fusion, starting with REGLU/GEGLU/SWIGLU for PoC.
Only CPU and CUDA right now, help needed to complete other backends!