[REFACTOR] Notification 조회 N+1 문제 해결

[jaewonLeeKOR]

PR 타입(하나 이상의 PR 타입을 선택해주세요)

• 기능 추가
• 기능 삭제
• 버그 수정
• 의존성, 환경 변수, 빌드 관련 코드 업데이트

반영 브랜치

refactor/#206/notificationN+1 -> develop

변경 사항

• Notification 조회 N+1 문제 해결
  • @EntityGraph 어노테이션을 이용하여 fetch join을 구현했습니다.

테스트 결과

기존의 쿼리

select
    n1_0.id,
    n1_0.created_at,
    n1_0.deleted_at,
    n1_0.member_id,
    n1_0.notification_log_id,
    n1_0.type,
    n1_0.updated_at 
from
    notification n1_0 
where
    n1_0.id<=? 
    and (
        n1_0.member_id=? 
        or n1_0.type=4 
        or n1_0.type=5
    ) 
order by
    n1_0.created_at desc 
offset
    ? rows 
fetch
    first ? rows only

select
    nl1_0.id,
    nl1_0.board_comment_id,
    nl1_0.board_id,
    nl1_0.body,
    nl1_0.created_at,
    nl1_0.deleted_at,
    nl1_0.question_id,
    nl1_0.subtitle,
    nl1_0.updated_at 
from
    notification_log nl1_0 
where
    nl1_0.id=?

수정된 쿼리

select
    n1_0.id,
    n1_0.created_at,
    n1_0.deleted_at,
    n1_0.member_id,
    nl1_0.id,
    nl1_0.board_comment_id,
    nl1_0.board_id,
    nl1_0.body,
    nl1_0.created_at,
    nl1_0.deleted_at,
    nl1_0.question_id,
    nl1_0.subtitle,
    nl1_0.updated_at,
    n1_0.type,
    n1_0.updated_at 
from
    notification n1_0 
left join
    notification_log nl1_0 
        on nl1_0.id=n1_0.notification_log_id 
where
    n1_0.id<=? 
    and (
        n1_0.member_id=? 
        or n1_0.type=4 
        or n1_0.type=5
    ) 
order by
    n1_0.created_at desc 
offset
    ? rows 
fetch
    first ? rows only

[tnals2384]

LGTM

[youngeun-dev]

LGTM !!!