mrlan
/
EnglishPal
4
0
Fork 11
Code Issues Pull Requests 22 Projects Releases Wiki Activity

WIP: Bug476-YuHuangtao #87

Closed
yuhuangtao wants to merge 0 commits from Bug476-YuHuangtao into master
pull from: Bug476-YuHuangtao
merge into: mrlan:master
Conversation 3 Commits - Files Changed -
yuhuangtao commented 2023-05-19 09:20:55 +08:00

与Alpha-snapshot20230511同步的分支，修改了单词的评级方式（添加了通过词根评级的方式），并重新修改了词库文件。规范用户和文章的评级。

与Alpha-snapshot20230511同步的分支，修改了单词的评级方式（添加了通过词根评级的方式），并重新修改了词库文件。规范用户和文章的评级。
yuhuangtao added 91 commits 2023-05-19 09:20:55 +08:00
yuhuangtao added 1 commit 2023-05-23 19:40:56 +08:00
mrlan commented 2023-05-23 19:49:35 +08:00
Owner

去掉了get_difficulty_level_for_user的多出的break

OK. Thanks

> 去掉了get_difficulty_level_for_user的多出的break OK. Thanks
yuhuangtao commented 2023-06-18 13:24:16 +08:00
Poster

当我在convert_test_type_to_difficulty_level和get_difficulty_level_for_user函数的开头和结尾添加

    time_start = time.time()

和

    time_end = time.time()
    print('convert_test_type_to_difficulty_level totally cost', time_end - time_start)

用于打印每次执行单词评级是两函数的运行时间时，本地运行的结果如下（分多次）：

convert_test_type_to_difficulty_level totally cost 0.009003639221191406
get_difficulty_level_for_user totally cost 0.009003639221191406

convert_test_type_to_difficulty_level totally cost 0.009998321533203125
get_difficulty_level_for_user totally cost 0.009998321533203125

convert_test_type_to_difficulty_level totally cost 0.010988235473632812
get_difficulty_level_for_user totally cost 0.010988235473632812

convert_test_type_to_difficulty_level totally cost 0.011525869369506836
get_difficulty_level_for_user totally cost 0.011525869369506836

耗时比官网要小很多，有没有可能是服务器的问题，如果不是，具体的改进方法有以下几种：

  • 修改数据库的文章表，添加文章难度字段，即：在管理员添加文章时，系统对文章进行评级，之后用户进行读取时直接从数据库中获取文章的难度，不再重复进行计算文章难度（能切实加快，但不是很推荐）
  • 针对用户表，添加一个字段，同上减少评级所需时间（可以做，但不推荐）
  • 尝试新建一个用户类，使其有一个单词的列表，在进入系统时基于此计算用户的等级，并将等级添加到用户实例的列表中的某个特定位置（勉强可以推荐）

以上三种方法，都是对于服务器无问题且运行耗时原因出自于评级部分情况下所作猜测，希望有所帮助

当我在convert_test_type_to_difficulty_level和get_difficulty_level_for_user函数的开头和结尾添加 ``` time_start = time.time() ``` 和 ``` time_end = time.time() print('convert_test_type_to_difficulty_level totally cost', time_end - time_start) ``` 用于打印每次执行单词评级是两函数的运行时间时，本地运行的结果如下（分多次）： ``` convert_test_type_to_difficulty_level totally cost 0.009003639221191406 get_difficulty_level_for_user totally cost 0.009003639221191406 ``` ``` convert_test_type_to_difficulty_level totally cost 0.009998321533203125 get_difficulty_level_for_user totally cost 0.009998321533203125 ``` ``` convert_test_type_to_difficulty_level totally cost 0.010988235473632812 get_difficulty_level_for_user totally cost 0.010988235473632812 ``` ``` convert_test_type_to_difficulty_level totally cost 0.011525869369506836 get_difficulty_level_for_user totally cost 0.011525869369506836 ``` 耗时比官网要小很多，有没有可能是服务器的问题，如果不是，具体的改进方法有以下几种： * 修改数据库的文章表，添加文章难度字段，即：在管理员添加文章时，系统对文章进行评级，之后用户进行读取时直接从数据库中获取文章的难度，不再重复进行计算文章难度（能切实加快，但不是很推荐） * 针对用户表，添加一个字段，同上减少评级所需时间（可以做，但不推荐） * 尝试新建一个用户类，使其有一个单词的列表，在进入系统时基于此计算用户的等级，并将等级添加到用户实例的列表中的某个特定位置（勉强可以推荐） 以上三种方法，都是对于服务器无问题且运行耗时原因出自于评级部分情况下所作猜测，希望有所帮助
👍 1
mrlan commented 2023-07-06 21:59:13 +08:00
Owner

已经并入 Alpha-snapshot

已经并入 Alpha-snapshot
mrlan closed this pull request 2023-07-06 21:59:13 +08:00

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: mrlan/EnglishPal#87
There is no content yet.
Delete Branch "Bug476-YuHuangtao"

Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?