EF Core Complex Query Method
As mentioned in a comment of mine, it's possible that there's a bug in the code. The OrderByDescending(p =&gt; p.UserLikes.Select(f =&gt; f.LikeStatus == LikeStatus.Like).Count() - p.UserLikes.Select(f =&gt; f.LikeStatus == LikeStatus.Dislike).Count()) call should always sort on a single value, 0. The call should be equal to OrderByDescending(p =&gt; p.UserLikes.Count() - p.UserLikes.Count()) because the Select method does not filter values. 

That being said, I'll consider it as OrderByDescending(p =&gt; p.UserLikes.Where(f =&gt; f.LikeStatus == LikeStatus.Like).Count() - p.UserLikes.Where(f =&gt; f.LikeStatus == LikeStatus.Dislike).Count()) from here on out. If this is not the case let me know and I'll delete this answer.

I see that you count likes and dislikes a couple of times in your queries, in the OrderByDescending method and in the LikeCount and DislikeCount properties in the final Select. Keeping in mind this consideration I'd change the query in the following:

ret = _dbEntitySet.AsNoTracking()
       .Where(p =&gt; p.PostId == postId &amp;&amp; p.IsPublished)
       .Include(p =&gt; p.UserLikes)
       .Select(p =&gt; new { DbEntity = p, LikeCount = p.UserLikes.Where(f =&gt; f.LikeStatus == LikeStatus.Like).Count(), DislikeCount = p.UserLikes.Where(f =&gt; f.LikeStatus == LikeStatus.Dislike).Count() })
       .OrderByDescending(p =&gt; p.LikeCount - p.DislikeCount)
       .Skip((reviewPageIndex - 1) * reviewPageSize)
       .Take(reviewPageSize)
       .Select(p =&gt; new PostModalReviewDisplay()
       {
           CommentCount = p.DbEntity.Comments.Count(),
           DislikeCount = p.DislikeCount,
           LikeCount = p.LikeCount,
           IsCurrentUserDisliked = p.DbEntity.UserLikes.Any(w =&gt; w.LikeStatus == LikeStatus.Dislike &amp;&amp; w.UserInfoId == currUserId),
           IsCurrentUserLiked = p.DbEntity.UserLikes.Any(w =&gt; w.LikeStatus == LikeStatus.Like &amp;&amp; w.UserInfoId == currUserId),

           Content = p.DbEntity.Content,
           Id = p.DbEntity.Id,
           UserInfo = new UserInfoExtraSmall()
           {
               AppUserId=p.DbEntity.UserInfo.AppUserId,
               Name=p.DbEntity.UserInfo.Name,
               Surname=p.DbEntity.UserInfo.Surname,
               ProfileImage=p.DbEntity.UserInfo.ProfilePicture.SmallPath
           }
       })


One more thing that comes to mind is to switch the comparison clauses in the IsCurrentUserDisliked and IsCurrentUserLiked properties. Note that the two versions could be the same in terms of performance, depending on the execution plan that the query optimizer generates, but personally I prefer to put the most selective comparison clause first. 

So, the final version would be the following:

ret = _dbEntitySet.AsNoTracking()
       .Where(p =&gt; p.PostId == postId &amp;&amp; p.IsPublished)
       .Include(p =&gt; p.UserLikes)
       .Select(p =&gt; new { DbEntity = p, LikeCount = p.UserLikes.Where(f =&gt; f.LikeStatus == LikeStatus.Like).Count(), DislikeCount = p.UserLikes.Where(f =&gt; f.LikeStatus == LikeStatus.Dislike).Count() })
       .OrderByDescending(p =&gt; p.LikeCount - p.DislikeCount)
       .Skip((reviewPageIndex - 1) * reviewPageSize)
       .Take(reviewPageSize)
       .Select(p =&gt; new PostModalReviewDisplay()
       {
           CommentCount = p.DbEntity.Comments.Count(),
           DislikeCount = p.DislikeCount,
           LikeCount = p.LikeCount,
           IsCurrentUserDisliked = p.DbEntity.UserLikes.Any(w =&gt; w.UserInfoId == currUserId &amp;&amp; w.LikeStatus == LikeStatus.Dislike),
           IsCurrentUserLiked = p.DbEntity.UserLikes.Any(w =&gt; w.UserInfoId == currUserId &amp;&amp; w.LikeStatus == LikeStatus.Like),

           Content = p.DbEntity.Content,
           Id = p.DbEntity.Id,
           UserInfo = new UserInfoExtraSmall()
           {
               AppUserId=p.DbEntity.UserInfo.AppUserId,
               Name=p.DbEntity.UserInfo.Name,
               Surname=p.DbEntity.UserInfo.Surname,
               ProfileImage=p.DbEntity.UserInfo.ProfilePicture.SmallPath
           }
       })


As a final thought, I agree with @AdrianoRepetti's comment: 


  Nothing better than to check generated SQL then they query plan and then measure...


Check the generated query plan for different versions and use the query that best suits your needs.