you. As a rule of thumb; cpu_affinity 1 favors repetitive short running tasks, while no affinity benefits longer running tasks. Note: The cpu_affinity setting requires the optional psutil module. 1.1 using result_group() is of course much faster than using fetch_group(), but it doesn’t offer the benefits of Django’s queryset functions. Note: Although fetch_group() returns a queryset, due to the nature

you. As a rule of thumb; cpu_affinity 1 favors repetitive short running tasks, while no affinity benefits longer running tasks. Note The cpu_affinity setting requires the optional psutil module. Footnotes using result_group() is of course much faster than using fetch_group(), but it doesn’t offer the benefits of Django’s queryset functions. Note Although fetch_group() returns a queryset, due to the nature

you. As a rule of thumb; cpu_affinity 1 favors repetitive short running tasks, while no affinity benefits longer running tasks. Note The cpu_affinity setting requires the optional psutil module. Requirements using result_group() is of course much faster than using fetch_group(), but it doesn’t offer the benefits of Django’s queryset functions. Note Although fetch_group() returns a queryset, due to the nature

you. As a rule of thumb; cpu_affinity 1 favors repetitive short running tasks, while no affinity benefits longer running tasks. Note: The cpu_affinity setting requires the optional psutil module. 1.3 using result_group() is of course much faster than using fetch_group(), but it doesn’t offer the benefits of Django’s queryset functions. Note: Although fetch_group() returns a queryset, due to the nature

you. As a rule of thumb; cpu_affinity 1 favors repetitive short running tasks, while no affinity benefits longer running tasks. Note The cpu_affinity setting requires the optional psutil module. Psutil using result_group() is of course much faster than using fetch_group(), but it doesn’t offer the benefits of Django’s queryset functions. Note Although fetch_group() returns a queryset, due to the nature

you. As a rule of thumb; cpu_affinity 1 favors repetitive short running tasks, while no affinity benefits longer running tasks. Note: The cpu_affinity setting requires the optional psutil module. Psutil using result_group() is of course much faster than using fetch_group(), but it doesn’t offer the benefits of Django’s queryset functions. Note: Although fetch_group() returns a queryset, due to the nature

you. As a rule of thumb; cpu_affinity 1 favors repetitive short running tasks, while no affinity benefits longer running tasks. Note The cpu_affinity setting requires the optional psutil module. Psutil using result_group() is of course much faster than using fetch_group(), but it doesn’t offer the benefits of Django’s queryset functions. Note Calling Queryset.values for the result on Django 1.7 or lower

you. As a rule of thumb; cpu_affinity 1 favors repetitive short running tasks, while no affinity benefits longer running tasks. 1.2. Configuration 11 Django Q Documentation, Release 0.7.8 Note: The cpu_affinity using result_group() is of course much faster than using fetch_group(), but it doesn’t offer the benefits of Django’s queryset functions. Note: Calling Queryset.values for the result on Django 1.7 or lower

you. As a rule of thumb; cpu_affinity 1 favors repetitive short running tasks, while no affinity benefits longer running tasks. Note: The cpu_affinity setting requires the optional psutil module. Psutil using result_group() is of course much faster than using fetch_group(), but it doesn’t offer the benefits of Django’s queryset functions. Note: Calling Queryset.values for the result on Django 1.7 or lower

you. As a rule of thumb; cpu_affinity 1 favors repetitive short running tasks, while no affinity benefits longer running tasks. 1.2. Configuration 11 Django Q Documentation, Release 0.7.11 Note: The using result_group() is of course much faster than using fetch_group(), but it doesn’t offer the benefits of Django’s queryset functions. Note: Calling Queryset.values for the result on Django 1.7 or lower