If one worker is the consumer of multiple queues, is concurrency per queue or global?

U

Unsmart•12/7/22, 9:22 PM

My question wasnt in response to you just a standalone question about queue regions

As far as latency I see about 500ms to my queue on a cold queue start and 250ms when its warmed up.

KKai If one worker is the consumer of multiple queues, is concurrency per queue or gl...

M

Matt Silverlock•12/7/22, 10:09 PM

There is no concurrency right now, but everything is/will be per queue. For example, a FIFO queue would have no concurrency. Each queue is the “atom” around which config is based.

K

KaiOP•12/7/22, 10:11 PM

Thanks. Asked about concurrency a few days ago and was told this would probably be a Config at some point and right now it's just no concurrency / concurrency = 1.
Per queue is great, thanks for the response!

Nnucks I'm running into an issue where an environment variable I set in my worker isn't...

M

Matt Silverlock•12/8/22, 2:17 PM

How are you trying to access your env var?

Environment

Environment

Environment

Environment is available to a

queue

queue

queue

queue handler as an arg, and so

Environment.<YOUR_ENV_VAR>

Environment.<YOUR_ENV_VAR>

Environment.<YOUR_ENV_VAR>

Environment.<YOUR_ENV_VAR> will exist.

M

Matt Silverlock•12/8/22, 2:25 PM

Got it. Let me see if we can repro.

K

kian•12/8/22, 2:57 PM

fwiw if you don't want to have to declare

Environment

Environment

Environment

Environment for every handler, you can type the

export default

export default

object literal

interface Environment {
  TOP_SECRET: string
}

interface Message {
  MY_EPIC_QUEUE_MESSAGE_INTERFACE_OR_WHATEVER: string
}

export default <ExportedHandler<Environment, Message>> {
  async fetch(req, env, ctx) {
    return new Response();
  },
  async queue(msg, env, ctx) {
    // do stuff
  }
}

interface Environment {
  TOP_SECRET: string
}

interface Message {
  MY_EPIC_QUEUE_MESSAGE_INTERFACE_OR_WHATEVER: string
}

export default <ExportedHandler<Environment, Message>> {
  async fetch(req, env, ctx) {
    return new Response();
  },
  async queue(msg, env, ctx) {
    // do stuff
  }
}

interface Environment {
  TOP_SECRET: string
}

interface Message {
  MY_EPIC_QUEUE_MESSAGE_INTERFACE_OR_WHATEVER: string
}

export default <ExportedHandler<Environment, Message>> {
  async fetch(req, env, ctx) {
    return new Response();
  },
  async queue(msg, env, ctx) {
    // do stuff
  }
}

interface Environment {
  TOP_SECRET: string
}

interface Message {
  MY_EPIC_QUEUE_MESSAGE_INTERFACE_OR_WHATEVER: string
}

export default <ExportedHandler<Environment, Message>> {
  async fetch(req, env, ctx) {
    return new Response();
  },
  async queue(msg, env, ctx) {
    // do stuff
  }
}

K

kian•12/8/22, 2:58 PM

once you go ExportedHandler you can't go back

K

kian•12/8/22, 2:58 PM

ever since @mrbbot mentioned it

Kkian fwiw if you don't want to have to declare `Environment` for every handler, you c...

I

Isaac McFadyen•12/8/22, 7:04 PM

Wah, TIL

J

John Spurlock•12/11/22, 6:23 PM

Question about introducing beta queues into a production worker: Ideally I'd like to set up an existing production worker as a consumer of a new queue and slowly start throwing non-critical background jobs at it. Will this have any hidden effects or limitations on the behavior/ deployment/performance of the existing fetch handler/DO part of this worker in any way? Wouldn't want

fetch

fetch

to be limited to a few colos for example, but totally fine if

queue

queue

queue

queue is.

M

maguayo•12/12/22, 2:08 PM

I need to add 400 messages to the queue. However, adding that many messages is slow. I was trying to add one message at a time and then create a new message once the previous one is finished (inside the task). However, it broke after 5 times. Is there a limit to prevent infinite loops or something?

If one worker is the consumer of multiple queues, is concurrency per queue or global?

Similar Threads

Similar Threads

Similar Threads