Skip to content
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

Daft equivalent of polars-lts-cpu #3564

Open
jpedrick-numeus opened this issue Dec 12, 2024 · 8 comments · Fixed by #3650
Open

Daft equivalent of polars-lts-cpu #3564

jpedrick-numeus opened this issue Dec 12, 2024 · 8 comments · Fixed by #3650
Labels
enhancement New feature or request p1 Important to tackle soon, but preemptable by p0

Comments

@jpedrick-numeus
Copy link

jpedrick-numeus commented Dec 12, 2024

Is your feature request related to a problem?

I often develop for an x86 environment on an M1 MacBook using an x86_64 docker container. Related to #1021 as I consider adding Daft to my technology stack it causes some issues when testing/building docker images that incorporate Daft.

Describe the solution you'd like

Polars solves this problem by providing a package polars-lts-cpu which runs ok on an M1 chipset inside an x86_64 docker container. I don't have any strong opinions on the particular solution. As an end user here I would only like to be able to run Daft on an x86_64 VM running on an M1 MacBook in a docker container.

Describe alternatives you've considered

Developing on a remote x86_64 based EC2 instance

Additional Context

No response

Would you like to implement a fix?

No

@jpedrick-numeus jpedrick-numeus added enhancement New feature or request needs triage labels Dec 12, 2024
@andrewgazelka
Copy link
Contributor

Hello @jpedrick-numeus can you specify which issues specifically you are experiencing? Is there some instruction set (say SIMD) that the x86 emulator you are using is not supoprting? Thank you :)

@jpedrick-numeus
Copy link
Author

jpedrick-numeus commented Dec 13, 2024

Hi @andrewgazelka

Hello @jpedrick-numeus can you specify which issues specifically you are experiencing? Is there some instruction set (say SIMD) that the x86 emulator you are using is not supoprting? Thank you :)

I'm not an expert regarding instruction sets. The module crashes on import.

$ python 
Python 3.10.15 | packaged by conda-forge | (main, Oct 16 2024, 01:24:24) [GCC 13.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import daft
Illegal instruction

I'm running Docker Machine on an M1 MacBook w/ an x86_64 docker image (mambaorg/micromamba) w/ the Rosetta emulator.

@kevinzwang
Copy link
Member

@samster25 do you know anything about this?

@samster25
Copy link
Member

Hi @jpedrick-numeus, I'm working on also publishing a LTS CPU version of Daft similarly to what you suggested!

@ccmao1130 ccmao1130 added p1 Important to tackle soon, but preemptable by p0 and removed needs triage labels Jan 8, 2025
@samster25 samster25 reopened this Jan 9, 2025
@samster25
Copy link
Member

Hi @jpedrick-numeus, We just started publishing a LTS version of daft here: https://pypi.org/project/daft-lts/0.4.2/#description

Can you try installing pip install daft-lts and verify that it works for you

@jpedrick-numeus
Copy link
Author

Hi @jpedrick-numeus, We just started publishing a LTS version of daft here: https://pypi.org/project/daft-lts/0.4.2/#description

Can you try installing pip install daft-lts and verify that it works for you

Sure thing! Thanks!

@samster25
Copy link
Member

hi @jpedrick-numeus how did it work out for you?

@jpedrick-numeus
Copy link
Author

jpedrick-numeus commented Jan 16, 2025

Hi @samster25 , I did some very light testing, but I've also noticed with the latest version of daft running on an x86_64 container on an M1 mac I'm able to run python -c "import daft" without it crashing without daft-lts installed. I'll definitely be testing this more extensively in the coming days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request p1 Important to tackle soon, but preemptable by p0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants