Code Monkey home page Code Monkey logo

daskqueue's Introduction

πŸ‘‹ Hello! I'm Amine.

  • πŸ€– I’m a Moroccan Freelance Datascientist working primarly computer vision state of the art problems.
  • 🌱 I’m currently building an end-to-end Document near-duplicate solution
  • πŸ’ͺ I’m the co-founder of Fitroulette App,a webRTC based application for enabling remote fitness sessions
  • πŸ’¬ You can ask me about ML/DL, Python, Golang, Distributed systems, React Native and WebRTC
  • πŸ“« You can reach me on @linkedIn
  • πŸ–‹οΈ I write about various technical subjects : blog
  • ⚑ I'm also a amateur kickboxer and grappler

πŸ“• Latest Blog Posts

⬆️ Latest Github Activity

  1. πŸ—£ Commented on #1118 in voxel51/fiftyone
  2. ❗️ Closed issue #4 in AmineDiro/Adversarial-Attacks
  3. πŸ—£ Commented on #4 in AmineDiro/Adversarial-Attacks
  4. πŸ’ͺ Opened PR #1118 in voxel51/fiftyone
  5. πŸ—£ Commented on #1097 in voxel51/fiftyone

πŸ“« Where to find me

Github LinkedIn Medium

daskqueue's People

Contributors

aminediro avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar

daskqueue's Issues

ZMQ communication layer

After multiple tests to profile the batch_submit method performance, I saw that bottleneck is the serialization in the distibuted.protocol . Basically when calling an attribute in an actor we use the RPCPool to send a send_recv call on communication layer which calls in return the protocol.dumps().

Msg size : 717
Protocol serialization : into list of 100002 protocol frames took 5.31s
Simple  cloudpickle.dumps() of message took 0.12s

This is too slow when submitting millions of tasks + I can optimize the storage layer to directly deal with serialized message.

I'll test using ZMQ for communication between client <-> QueuePool and Queue<-> workers.

Suggestion

Hi,
I have a react based webapp integrated with Django as a backend, the current challenge we are facing in file uploads like we are expecting 3-5lac file upload of average size say 5Mb each file. Currently we are implemented using celery and redis but it is not efficient to handle this much request. I wanted to know if dask queue can handle this efficiently. Can anyone please help me on this.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo 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.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.