anilmaddala
I am a newbie to Elixir, FP and trying to evaluate Elixir/Phoenix backend for a Machine Learning based application. My original idea was to use Elixir<->Rust<->Tensorflow on the backend server.
On doing some initial search, I found references claiming that Elixir is not suitable for process intensive tasks.
So my question would be, what/why is the limitation present? Where to draw the line for elixir in terms of which task is process intensive?
Thanks
Where Next?
Trending in Discussions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Master modern tools, write cleaner code, and tackle real-world challenges with Manning books, videos, and courses. Start building today.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #ecto-query
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
LostKobrakai
Afaik one of the downsides in computationally expensive tasks is because of immutable data. For certain problems there simply are more performant algorithms around for mutable data then you have for immutable data. Sometimes you can mimic those by using ets, which is an in memory database within the beam (so mutable), but I’m not sure what the determining factors are for when this works or not.
hauleth
CPU intensive tasks in Elixir will have the problems @LostKobrakai mentioned, however if you will use NIF or any other interoperability approach offered by BEAM then this will not be much of the problem (your example with Elixir ↔ Rust is great example of that). So if you want that approach then go for it, just shift CPU-intensive work to the Rust (or any other language) and keep Elixir as a frontend for IO-intensive work.