mossy walrus
REST framework
This article(https://hakibenita.com/django-rest-framework-slow) suggests that ModelSerializers are slower than general serializers.
According to this post's(https://www.reddit.com/r/django/comments/sesi0s/modelserializer_or_serializer_which_one_is_better/) discussion there is no significant difference 😦 and normal serializers performance is unstable and sometimes performs worse.
I wonder if anyone else tested it.
sour verge
If your model is not nested, using queryset.values is significantly faster than either
this is for read only purposes though
as in haki benita's article, passing read_only=True to model serializer also makes serialization faster
craggy grove
REST framework
This article(https://hakibenita.com/django-rest-framework-slow) s...
From my experience, Serializers are faster than ModelSerializers. Serializers do the exact thing they are told to do. No series of underground validations. No model validation etc. Those things tend to slow down the speed. So yeah
mossy walrus
From my experience, Serializers are faster than ModelSerializers. Serializers do...
model serializer allows cleaner code though, idk if the performance gain is better enough to give up the simplicity
tiny jetty
What is the API that you will be building that is using either model or general serializer.
I would think of that first before choosing either.
craggy grove
model serializer allows cleaner code though, idk if the performance gain is bett...
Yeah I totally understand you. But from my perspective as someone who always chooses speed, I’d choose serializers.Serializer, afterall I don’t think you would regard models.Model as an unclean code. Little things like that. For example, using tuples over list in some cases because tuple is faster performance wise. Negligible but there anyways.