Comments (5)
But why can't we use the wormhole version when the intrinsics are not present, like in Release?
We can definitely use this approach but only in FFx because wormhole is FFx specific. For non-FFx case, we will have to use the slow fallback gemm. So the solution would be:
- In Firefox browser
- Use
mozIntGemm
(i.e. optimized gemm) if available else use wormhole
- Use
- All other browsers
- Use pure wasm based gemm without any wormhole
To support this workflow, the extension:
- Should have the capability to differentiate b/w various browser environments i.e. Firefox Nightly vs Firefox non-Nightly vs Non-Firefox). This is possible. Right?
- Should download the specific
bergamot-translator-worker.js
andbergamot-translator-worker.wasm
artifacts based on the browser environment (because these artifacts are different for wormhole than the non-wormhole case) and work with them. #82 is a prerequisite for achieving this task.
from firefox-translations.
We will see speed-up only if the extension is a privileged one. Otherwise, the extension will fallback to extremely slow fallback gemm.
from firefox-translations.
Well, if the extension is not privileged, it won't work at all, since the UI also requires privileged permissions. There's no scenario where this can work at all if not privileged.
But why can't we use the wormhole version when the intrinsics are not present, like in Release?
from firefox-translations.
@abhi-agg the extension won't work on non-FF environments anyway, since it utilizes privileged APIs not available in other browsers, so yes, in other browsers, in the context of a regular webpage, it should Use pure wasm based gemm without any wormhole
Being specific to your question:
1 - Yes.
2 - Yes.
from firefox-translations.
@abhi-agg the extension won't work on non-FF environments anyway, since it utilizes privileged APIs not available in other browsers, so yes, in other browsers, in the context of a regular webpage, it should
Use pure wasm based gemm without any wormhole
This reduces the overall complexity then. Since this extension won't work on non-FFx environments, there is no need to load/import the translator artifacts that support the non-FFx browsers (i.e. non-wormhole ones) in this extension. This implies:
To support this workflow, the extension:
1. Should have the capability to differentiate b/w various browser environments i.e. Firefox Nightly vs Firefox non-Nightly vs Non-Firefox). This is possible. Right? 2. Should download the specific `bergamot-translator-worker.js` and `bergamot-translator-worker.wasm` artifacts based on the browser environment (because these artifacts are different for wormhole than the non-wormhole case) and work with them.
We don't need to do any of this because the extension should use optimized gemm whenever it is available and resorts to use wormhole-based fallback gemm otherwise. This is achievable using only 1 set of artifacts and has been fixed in #111. Hence closing this issue.
from firefox-translations.
Related Issues (20)
- User preferences are not respected HOT 1
- A good model to feed English to Japanese translation to HOT 7
- Wrong translation (repetition) HOT 1
- Suggestion: Ability to hide toolbar after translation is completed HOT 1
- Japanese language support HOT 1
- Error when highlighting in red is enabled HOT 1
- [Language Request] Add Korean Translation HOT 1
- [Language Request] Add Romanian Translation HOT 1
- Video is not accessible, actual documentation would be better HOT 1
- "An error occurred while loading the translation engine" with Firefox and Linux HOT 2
- Request: set <html lang="..."> attribute HOT 1
- REQUEST: Add an option to restore the Translation Banner (if user has accidentally clicked "Never offer translations") HOT 3
- Add ability to choose destination language other than browser language HOT 3
- Use dictionary lookup for single words HOT 1
- Translate button is not visible in almost all Light themes HOT 8
- Typos in translation russian->english HOT 6
- Please don't file issues, bugs and feature requests are now reported on Bugzilla (https://bugzilla.mozilla.org/) and language requests on Mozilla Connect (https://connect.mozilla.org/) HOT 2
- Japanese language translation support HOT 1
- From external webextension HOT 3
- Different behaviours between Firefox 115 esr w/ translation extension and Firefox 117 beta with support built-in HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from firefox-translations.